Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add MatthewYe/opencode-toolbox --skill opencode-plugin-scaffoldgit clone --depth 1 https://github.com/MatthewYe/opencode-toolboxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/matthewye/opencode-toolbox/opencode-plugin-scaffold)<a href="https://agentmods.dev/skills/matthewye/opencode-toolbox/opencode-plugin-scaffold"><img src="https://agentmods.dev/badge/skills/matthewye/opencode-toolbox/opencode-plugin-scaffold/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/matthewye/opencode-toolbox/opencode-plugin-scaffold"><img src="https://agentmods.dev/badge/skills/matthewye/opencode-toolbox/opencode-plugin-scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00079 | $0.00851 |
| Opus 5.5 | $0.00032 | $0.00340 |
| Sonnet 5.5 | $0.00016 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
opencode-plugin-scaffold scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Plugin Scaffold
Create a new opencode plugin from scratch, or align an existing project with plugin conventions.
Architecture
An opencode plugin is a TypeScript module exporting an async function:
async (PluginInput) => hooks object
PluginInput includes: project, client, $ (BunShell), directory, worktree.
Hooks are organized by domain — see references/hooks.md for the full catalog.
Two deployment modes:
| npm | local | |
|---|---|---|
| Location | Standalone dir, published to npm | .opencode/plugins/ or ~/.config/opencode/plugins/ |
| Install | "plugin" in opencode.json |
Auto-discovered, no config needed |
| Build | bun build → dist/ |
Run .ts directly (Bun native) |
| Naming | Prefix opencode-* |
No requirement |
| Deps | Listed in package.json |
External deps go in .opencode/package.json |
Workflow
Create from scratch
Run bash scripts/init.sh for interactive prompts (mode, name, path, publish). The script generates a complete scaffold with a working example tool.
If the script is unavailable, the agent can generate files manually — the script's gen_* shell functions serve as the canonical templates (read scripts/init.sh to find them). Key templates:
gen_package_json— package.json with correct deps and scriptsgen_tsconfig_json— tsconfig extending@tsconfig/node22gen_index_ts_with_tool— entry with a working example tool (default fornpmmode)gen_index_ts_empty— minimal empty skeleton (used forlocalmode and--fix)
After scaffolding: bun install && bun run src/index.ts to verify the plugin loads.
Fix an existing project
Run bash scripts/init.sh --fix <path>. The script detects what's missing and adds only what's needed — it never overwrites existing files.
If running manually without the script, follow this detection order:
package.jsonexists? — if not, generate one. If yes, ensure@opencode-ai/pluginin dependencies.tsconfig.jsonexists? — if not, generate one.- Entry file (
src/index.tsorindex.ts) exists? — if not, generate empty skeleton. - Entry file exports a
Pluginfunction? — if not, warn and abort (don't overwrite user code). dist/directory (npm mode only)? — hint about build setup if missing.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 78 lines · 79 tokens per session scan A 47ccfb6820ce
opencode-plugin-scaffold is a skill published in the GitHub repository MatthewYe/opencode-toolbox (5 stars, last pushed 3mo ago), licensed MIT. It adds 79 tokens to every session and 851 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…