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-architect

v0.7.0

Published

OpenCode plugin and CLI with ten specialist agents for agent skills, slash commands, custom tools, plugins, and MCP server integration

Readme

opencode-architect

npm version License: MIT OpenCode plugin

Ten specialist agents that design, build, and package OpenCode extensions — agent skills, slash commands, custom tools, plugins, and MCP server integrations — right inside your AI coding assistant.

opencode-architect is an OpenCode plugin and CLI that ships a suite of AI agent experts for OpenCode work: designing agents, creating skills and slash commands, building plugins and custom tools, integrating MCP servers, and packaging extensions for npm. Install it once and every specialist agent is available in your coding sessions.

Quick start: install the OpenCode plugin suite

Option 1 — Install as an OpenCode plugin

Add the package to the plugin array in your OpenCode config — .opencode/opencode.json in your project, or ~/.config/opencode/opencode.json for all projects:

{
  "plugin": ["opencode-architect"]
}

The plugin registers the full agent suite at startup, with self-contained bundled references — no network sync.

Option 2 — Install with the CLI (bunx or npx)

Copy the agents, references, and templates straight into your OpenCode directories, where you can read and modify every file:

# Project scope (default): copies into ./.opencode/
bunx opencode-architect install

# Global scope: copies into ~/.config/opencode/
bunx opencode-architect install --scope global

npx opencode-architect install works the same way if you prefer npm's runner.

Useful flags and commands:

bunx opencode-architect status                  # show install mode and version for a scope
bunx opencode-architect uninstall               # remove exactly the files a copy install wrote
bunx opencode-architect install --force         # overwrite locally modified files, switch a scope from plugin to copy install
bunx opencode-architect --help                  # full usage

A copy install writes 10 agents into agents/, 9 reference docs into opencode-architect/references/, and 9 starter templates into opencode-architect/templates/ of the scope base, plus an opencode-architect.json manifest that tracks versions and file hashes for safe upgrades. Relative reference paths inside agents are rewritten to absolute paths at install time.

Plugin install and copy install are mutually exclusive per scope — the CLI refuses to copy over an existing plugin entry unless you pass --force.

What you get: ten specialist OpenCode agents

Ten specialist agents, one router:

| Agent | What it does | | --- | --- | | opencode-architect | Routes OpenCode meta tasks to the right specialist — agents, skills, commands, tools, plugins, MCP setup, packaging, publishing | | opencode-agent-designer | Designs OpenCode agents and orchestrator subagents — roles, constraints, tools, permissions | | opencode-skill-creator | Creates OpenCode skills in .opencode/skills — SKILL.md, frontmatter, progressive disclosure | | opencode-command-crafter | Creates OpenCode slash commands in .opencode/commands — prompt templates, $ARGUMENTS, frontmatter | | opencode-tool-builder | Creates OpenCode custom tools in .opencode/tools — Zod schemas and execute logic | | opencode-plugin-engineer | Builds OpenCode plugins in .opencode/plugins — event hooks, custom tools, TypeScript | | opencode-mcp-integrator | Configures MCP servers and tool scoping in opencode.json — local/remote servers, permissions | | opencode-packager | Packages OpenCode extensions for local sharing across projects — file:/// plugin packages | | opencode-publisher | Publishes OpenCode extensions to npm — transforms local packages into distributable ones | | opencode-extension-auditor | Analyzes .opencode/ contents and reports packaging readiness — inventory, dependencies, complications |

Also bundled and installed with the agents:

  • References — self-contained docs covering stable OpenCode fundamentals: agents, commands, config, MCP servers, plugins, prompt engineering, skills, tools, plus worked one-shot examples
  • Templates — starter files for new skills, plugins, package manifests, and TypeScript configs

When to use these OpenCode agents

Reach for opencode-architect whenever you want to:

  • Spin up new OpenCode agents with consistent frontmatter and tool permissions
  • Create agent skills and slash commands with solid prompt engineering
  • Build OpenCode plugins and custom tools in TypeScript
  • Integrate MCP servers into your OpenCode setup with confidence
  • Package and publish your extensions so other developers can install them

Requirements

  • OpenCode — the AI coding assistant the plugin extends
  • Bun — runs the plugin and the CLI (bunx); if you use npx, Bun must still be on your PATH because the CLI ships as TypeScript

Development

Install dependencies:

bun install

Type check:

bun run check

Run the test suite:

bun test

Acknowledgements

  • OpenCode - The AI coding assistant that makes this plugin possible
  • Bun - The fast all-in-one JavaScript runtime
  • qforge - Original developer of this project