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/khaledzag/claude-opencode/opencode-implementnpx skills add khaledzag/claude-opencode --skill opencode-implementgit clone --depth 1 https://github.com/khaledzag/claude-opencodeWhat 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.00184 | $0.02356 |
| Opus 5 | $0.00092 | $0.01178 |
| Sonnet 5 | $0.00037 | $0.00471 |
| Haiku 4.5 | $0.00018 | $0.00236 |
Grade A, and why
opencode-implement 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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
opencode-implement
Plan a coding task with Claude, get user approval on the plan, then hand the plan file to OpenCode to execute. Claude verifies the result against the plan when OpenCode returns.
This skill is for plan-first workflows. If the user wants direct delegation without a planning phase, use opencode-delegate instead.
When to use this skill
- The user asks to "plan and implement", "plan then delegate", "design first", "think through the approach".
- The task is non-trivial (multi-file, ambiguous scope, architectural decisions).
- Getting the design right matters as much as getting it done.
- When in doubt between this and
opencode-delegate, prefer this one — planning is cheap, bad implementation without planning is expensive.
When NOT to use this skill
- The user explicitly wants direct delegation ("just run this", "skip planning", "delegate directly") → use
opencode-delegate. - Trivial fixes, single-line changes, obvious one-file edits → just let Claude do it.
- Pure conversation, explanation, or debugging with no code writing → neither skill applies.
- When
opencodeisn't installed — stop and direct the user to install, don't silently fall back.
Interaction rules (load-bearing)
Follow these strictly — the skill's UX depends on them.
Use AskUserQuestion for every decision point. Do not compress multiple decisions into a single prose message with numbered questions.
Decision points that must use AskUserQuestion, each as its own call:
- Plan approval (Phase 3) — "Looks good", "Needs changes", "Cancel".
- Model selection (Phase 4a) — authed models as options plus "Other".
- Permission selection (Phase 4b) — "Read-only", "Implement", "Implement, no shell".
Ask them in sequence. Use the answer to one before asking the next. Do not batch.
If you find yourself writing "Before I delegate, a few confirmations:" followed by a numbered list — stop. That's the failure mode. Back up and use AskUserQuestion for the next single decision.
What ships with it
7 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.
- 2d ago First seen · 176 lines · 184 tokens per session scan A 249291cfb19a
opencode-implement is a skill published in the GitHub repository khaledzag/claude-opencode (9 stars, last pushed 4mo ago), licensed MIT. It adds 184 tokens to every session and 2,356 once invoked, about $0.0009 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…