npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

opencode-orca-hint

v0.1.0

Published

Injects a system-prompt hint into opencode when running inside the Orca app, so the agent reaches for the orca-cli skill and Orca's tools instead of raw shell workarounds.

Readme

opencode-orca-hint

opencode plugin that tells the agent when it is running inside the Orca app, so it reaches for Orca's own tooling instead of falling back to raw shell workarounds.

Why

When opencode runs inside an Orca-managed environment, the agent often doesn't realize it has dedicated tooling available. Instead of using orca-cli and the orca-cli skill for Orca-managed state — worktrees, folder contexts, terminals, repos, automations, artifacts, worktree comments, and the browser embedded inside Orca — it reaches for ad hoc PTYs, git worktree, Playwright, or Computer Use.

This plugin detects the Orca environment and injects a short hint into the system prompt, so the agent routes Orca-related work through Orca's CLI and skills.

How it works

  • Detects the environment through environment variables exported by the Orca app (ORCA_CLI_COMMAND, ORCA_DEV_REPO_ROOT, or any ORCA_* variable).
  • When detected, appends a few lines to the system prompt via the experimental.chat.system.transform hook.
  • When not detected, the plugin is a no-op — no overhead in regular terminals.

Install

opencode plugin install opencode-orca-hint

Or add it to the plugin array in your opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-orca-hint"]
}

Restart opencode after installing.

Verify

Inside Orca's terminal, open opencode and ask:

Paraphrase what your system prompt says about what environment you are running in.

It should answer that it is running inside the Orca app, not a standalone terminal, and mention orca-cli. Repeat the same question in a regular terminal — there it should not mention Orca at all.

Requirements

License

MIT