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 agentmods add skills/zhouqingweidev-ops/opencode-mcp/opencode-usenpx skills add zhouqingweidev-ops/opencode-mcp --skill opencode-usegit clone --depth 1 https://github.com/zhouqingweidev-ops/opencode-mcpWhat 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 | $0.00089 | $0.01108 |
| Opus 5 | $0.00044 | $0.00554 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
opencode-use 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 yesterday.
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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
opencode-use
This Skill is for the Claude Code primary agent. Claude keeps full ability to read, edit, test, reason, use native tools, and use Claude subagents. OpenCode is an optional execution channel, not a replacement for Claude. Do not send every task to OpenCode.
Choose one execution path
native_claude: Claude works directly. Choose this for tiny changes, code already understood by Claude, sensitive or high-risk files, frequent user interaction, architecture judgment, review/reasoning, or an explicit request for Claude to do the work. Do not callopencode-router-mcp.claude_subagent: use Claude Code's native subagent for parallel research, independent code/security review, Claude-specific capabilities, or an explicit request for a Claude subagent. Never replace it with OpenCode.opencode_run: use OpenCode for a bounded, one-shot, low-cost/free, mechanically verifiable task when Claude has not already done the full analysis. Prefer small bugs, lint/type fixes, test additions, simple refactors, docs, CSS, and repetitive edits.opencode_session: use OpenCode when persistent status, review, revision, long-running work, retained context, or iterative visual work is genuinely useful. Model failover is handled internally by the MCP in either run or session mode and does not by itself require a session.
User instructions have highest priority: Claude request → native_claude; Claude subagent request → claude_subagent; OpenCode request → an OpenCode path; free-model request → maxTier: cheap, freeOnly: true, and allowTierUpgrade: false; OpenCode prohibition → do not call the MCP.
OpenCode delegation
The Skill decides among the four paths. The MCP only manages OpenCode-internal tier, model, run/session mode, failover, and compact state after Claude has selected OpenCode. MCP mode: auto never chooses Claude or a Claude subagent.
Use only these high-level tools: opencode_delegate, opencode_status, opencode_review, opencode_revise, opencode_abort, opencode_models, and opencode_usage. Do not call or suggest hidden upstream low-level tools.
What ships with it
5 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.
- yesterday First seen · 46 lines · 89 tokens per session scan A f77d08b0a782
opencode-use is a skill published in the GitHub repository zhouqingweidev-ops/opencode-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,108 once invoked, about $0.0004 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.