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

@chamba/opencode-extras

v1.4.0

Published

Optional OpenCode extras for chamba: slash commands + subagents installer

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

thelord07thelord07

Keywords

chambaopencodemcpslash-commandssubagents

Readme

@chamba/opencode-extras

Optional OpenCode extras for chamba: slash commands and subagents on top of the chamba MCP server.

Only need the tools? Point OpenCode at @chamba/mcp directly (see the OpenCode setup guide). This package adds the /commands and subagents on top — the same ones Claude Code gets.

Usage

npx @chamba/opencode-extras@latest install          # commands + subagents + register the MCP server
npx @chamba/opencode-extras@latest install --global  # + npm i -g @chamba/mcp; launch the binary, not npx
npx @chamba/opencode-extras@latest install --force   # overwrite existing files
npx @chamba/opencode-extras uninstall         # remove them
npx @chamba/opencode-extras --version

It installs into ~/.config/opencode/ (or $OPENCODE_CONFIG_DIR):

  • Commands → commands/: /ticket, /triage, /qa, /design, /orq, /map, /workspace, /worktrees, /recall, /vault.
  • Subagents → agents/ (mode: subagent): planner, implementer, reviewer, tester, qa, diagnostician.
  • MCP server → chamba under "mcp" in opencode.json (preserves any others).

Then restart OpenCode and run /ticket ABC-123 (or /triage, /qa, …) in the TUI.

How it relates to Claude Code

The command and subagent prompts are shared with @chamba/claude-extras — one source of truth, translated to OpenCode's format on install:

  • Commands keep description and the $ARGUMENTS body; the Claude-Code-only argument-hint is dropped.
  • Subagents become mode: subagent, with the model emitted as OpenCode's provider-scoped string (anthropic/<model>) taken from your chamba per-agent config (~/.chamba/config.json). A non-Anthropic model is left unset so OpenCode uses its own default. chamba's effort has no OpenCode equivalent, so it's dropped.

chamba never calls a model — this only tells OpenCode's model how to delegate. Configure the per-agent reparto with npx @chamba/claude-extras config <show|set|preset|…>; both editors read the same ~/.chamba/config.json.

--global — a steadier launch

By default the MCP server is registered as npx -y @chamba/mcp, which re-resolves the package from npm on every spawn. install --global runs npm i -g @chamba/mcp and registers the chamba-mcp binary instead — no per-launch npm, so the connection is far less likely to drop. Falls back to the npx launcher if the global install can't run.

License

MIT