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 ZaxbyHub/opencode-swarm --skill deep-researchgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/deep-research)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/deep-research"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/deep-research.svg" alt="Measured on agentmods" 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.00082 | $0.02504 |
| Opus 5 | $0.00041 | $0.01252 |
| Sonnet 5 | $0.00016 | $0.00501 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
deep-research 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 today.
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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Research Protocol
Read-only, multi-source, fact-checked research that produces a cited report. The
architect is the orchestrator: it owns retrieval (web_search + web_fetch),
decomposes the question, runs an iterative gather→assess→re-plan loop, dispatches
parallel sme workers for synthesis, verifies claims against sources with 2
reviewers, challenges high-stakes claims with the critic, and writes the final
answer. This mode does NOT mutate source code, does NOT delegate to coder, and
does NOT call declare_scope.
MODE: DEEP_RESEARCH
Step 0 — Parse Header
Parse the [MODE: DEEP_RESEARCH ...] header to extract:
depth: standard | exhaustive (default: standard)max_researchers: integer 1..6 — parallel synthesis workers per round (default: 3, or 5 for exhaustive)rounds: integer 1..4 — maximum iterative research rounds (default: 2, or 3 for exhaustive)output: report | brief (default: report)- the trailing text is the
question
If the header is malformed or the question is empty, report the error and stop.
Step 1 — Pre-flight (always run first)
Read council.general from the resolved opencode-swarm config (global
~/.config/opencode/opencode-swarm.json first, then project
.opencode/opencode-swarm.json override). If council.general.enabled is not
true OR no search API key is configured (neither council.general.searchApiKey
nor TAVILY_API_KEY / BRAVE_SEARCH_API_KEY), surface to the user:
"Deep research needs external search. Set council.general.enabled: true and configure a search API key (Tavily or Brave) in global ~/.config/opencode/opencode-swarm.json or project .opencode/opencode-swarm.json."
Then STOP. Do NOT produce ungrounded research from training memory.
(web_search requires the key; web_fetch only requires the enabled flag and is
architect-only. The sme workers do NOT have web_fetch and must not be expected to
fetch sources. An sme may have web_search, but in this mode it synthesizes only
from the evidence you gather — do NOT rely on sme-side searching; pass it the
RESEARCH CONTEXT.)
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.
- today Changed · +3 lines 753e50f107f5
- 7d ago First seen · 202 lines · 82 tokens per session scan A 3ceb40946333
deep-research is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (463 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,504 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-30.
Other skills, from other repositories
armada-contract
Co-write an armada contract (REQUIREMENTS.md) one question at a time. Use when drafting or updating a feature contract before implementation.
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
selftune
Self-improving skills toolkit that watches real agent sessions, detects missed triggers, grades execution quality, and improves skill packages through evals, replay, baselines, review, and post-deploy watch. Use when verifying or publishing a skill, improving instructions or routing, checking skill health, grading…
armada-dispatch
Dispatch subagents in parallel with disjoint file scope. Use when facing 2+ independent tasks, multiple files, or parallel phases. Triggers on: parallelize, dispatch subagents, run in parallel.
armada-voyage-finish
Voyage-finalization ritual. Load at voyage end, dispatch a galleon subagent to rebase, fix TODO PR refs, regen scaffold, push, open/update PR. Triggers on: finish voyage, finalize, rebase, PR.
armada-ledger
Pick the right ledger for a finding. Use when writing defects, adversarial findings, or security findings. Triggers on: ledger, defect, adversarial, security finding, DEF-001, ADV-001, SEC-001.