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 sssemil/SKILLS --skill opencode-delegategit clone --depth 1 https://github.com/sssemil/SKILLSWrote 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/sssemil/skills/opencode-delegate)<a href="https://agentmods.dev/skills/sssemil/skills/opencode-delegate"><img src="https://agentmods.dev/badge/skills/sssemil/skills/opencode-delegate/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/sssemil/skills/opencode-delegate"><img src="https://agentmods.dev/badge/skills/sssemil/skills/opencode-delegate.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.00047 | $0.01497 |
| Opus 5.5 | $0.00019 | $0.00599 |
| Sonnet 5.5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
opencode-delegate 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 2mo 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safe OpenCode Delegate
Use this skill when the user wants Codex to orchestrate coding work while OpenCode performs the implementation inside the safe-claude sandbox.
Codex is the planner, operator, reviewer, and validator.
OpenCode is the implementer.
Run OpenCode only through:
safe-opencode run
Do not use plain opencode for delegated implementation.
Default stance
Do not write the main implementation yourself.
Use safe-opencode for:
- finding relevant code
- tracing behavior
- implementation
- refactors
- migrations
- bug fixes
- test generation
- repetitive edits
- boilerplate
- mechanical cleanup
Codex remains responsible for:
- understanding the request
- choosing scope
- choosing the model
- writing the OpenCode job
- reviewing the diff
- running validation
- deciding whether the patch is acceptable
Model routing
Use the smallest useful DeepSeek model.
Fast path
Use DeepSeek v4 Flash for simple, bounded, low-risk jobs:
- find where something is implemented
- inspect a small area of the repo
- explain a local behavior
- make a one-file or very small edit
- add a small test
- fix an obvious typo, import, or error handling issue
- triage a test failure
- produce boilerplate inside an existing pattern
- do a narrow rename or cleanup
Fast command:
safe-opencode run --model deepseek/deepseek-v4-flash --title "codex-delegate: <short-task-name>" "<single focused job>"
Pro path
Use DeepSeek v4 Pro for heavier work:
- multi-file changes
- architecture-sensitive changes
- unclear bugs
- migrations
- public API changes
- security-sensitive logic
- database or persistence changes
- complicated test failures
- work where a bad patch would be costly to unwind
Pro command:
safe-opencode run --model deepseek/deepseek-v4-pro --title "codex-delegate: <short-task-name>" "<single focused job>"
If a Fast job returns a weak, broad, or confused patch, do not keep pushing it. Escalate once to Pro with a sharper prompt.
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.
- 2mo ago First seen · 302 lines · 47 tokens per session scan A 522f21746b25
opencode-delegate is a skill published in the GitHub repository sssemil/SKILLS (2 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,497 once invoked, about $0.0002 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…