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/dasdigitalemomentum/opencode-processing-skills/delegate-analysisnpx skills add DasDigitaleMomentum/opencode-processing-skills --skill delegate-analysisgit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWhat 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.00039 | $0.00514 |
| Opus 5 | $0.00019 | $0.00257 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
delegate-analysis 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Delegate Analysis
Use one of the following modes. The primary should name the mode, scope, and question explicitly.
Modes
code-exploration
- Orient with file search, then read only the key files.
- Trace dependencies one level further only when needed.
- Return findings with concrete file paths and symbols.
targeted-reading
- Use the named files as scoped starting points and retrieve only what answers the question.
- Extract only the facts needed to answer the question.
- Organize the result by topic or file, with line references where useful.
web-research
- Prefer authoritative primary sources.
- Cross-check important claims when practical.
- Return a concise synthesis with source URLs and explicit uncertainty.
- This is delegate work: use
retrieveronly to crawl or fetch already-selected sources, not for open-ended search, source selection, or cross-source judgment.
deep-dive
- Start at the named entry point and follow relevant indirections until the question is answered.
- Map the code or data path with file and symbol evidence.
- Highlight non-obvious behavior, assumptions, and unresolved gaps.
Rules
- Default to read/analyze/verify. Do not edit files.
- Stay within the delegated scope.
- Directly read scoped source, docs/plans, symbols, and compact targeted evidence. Keep uncurated bulk evidence out of the delegate context: use a reliable focused filter when sufficient; otherwise route the raw artifact, command, or path plus a focused question to
retriever, including coherent multi-file evidence. Numeric tool truncation is a safety net, not the routing rule. - Spool potentially verbose command output to a predictable path under
/tmp/opencode/; retain only path, command, exit status, and compact metadata/evidence. This supports same-machine continuation after an interruption, not reboot durability. - The parent owns synthesis and verifies only evidence that materially supports its conclusions rather than repeating broad retrieval.
- If the task becomes a review, artifact authoring task, or implementation task, stop and ask the primary to route through the matching skill.
- Return a compact digest, not raw file contents or long logs.
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 · 51 lines · 39 tokens per session scan A 3f93cf0749ad
delegate-analysis is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (59 stars, last pushed 23d ago), licensed MIT. It adds 39 tokens to every session and 514 once invoked, about $0.0002 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-30.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…