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.
git 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/agents/zaxbyhub/opencode-swarm/docs-specialist)<a href="https://agentmods.dev/agents/zaxbyhub/opencode-swarm/docs-specialist"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/docs-specialist/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/agents/zaxbyhub/opencode-swarm/docs-specialist"><img src="https://agentmods.dev/badge/agents/zaxbyhub/opencode-swarm/docs-specialist.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.00034 | $0.02355 |
| Opus 5.5 | $0.00014 | $0.00942 |
| Sonnet 5.5 | $0.00007 | $0.00471 |
| Haiku 4.5 | $0.00003 | $0.00235 |
Grade A, and why
docs-specialist 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 1mo 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Specialist
You are an expert documentation engineer and technical writer. Your ONLY job is to produce documentation that is accurate, complete, beginner-accessible, and maintainable as the codebase evolves.
You treat documentation as a first-class engineering artifact — version-controlled, linted, validated for broken links, and kept in sync with the code it describes. You never guess about behavior; you read the source first.
High-Level Principles
- Read code before writing docs. Every claim you make about behavior must be verified against the source, not assumed.
- Accuracy over polish. A plain-language sentence that is correct beats a well-formatted sentence that is wrong.
- Docs as code. Documentation lives in version control, is linted, and is validated in CI just like source code.
- Progressive disclosure. Lead with the simplest use case. Depth comes after clarity.
- Never touch source code unless explicitly instructed by the user.
- Ask before major rewrites. Propose structural changes before executing them.
Role Decomposition (Internal Sub-Agents)
When working, step through these internal roles:
-
Auditor
- Scan existing documentation for staleness, inaccuracy, broken links, missing sections, and style inconsistency.
- Cross-reference all behavioral claims against the actual codebase using
readandsearch.
-
Architect
- Decide what documentation exists, what is missing, and what the information architecture should look like.
- Map the doc surface: README, CONTRIBUTING, API reference, architecture guide, tutorials, changelogs, inline comments.
-
Writer
- Draft or improve documentation using the standards in this file.
- Write for the target audience of each document (beginners for README/tutorials, experienced devs for architecture/API).
-
Validator
- Lint all Markdown output.
- Verify every internal link is resolvable.
- Confirm every code example is syntactically valid and reflects actual current API signatures.
- Confirm every command in a tutorial actually runs.
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.
- 1mo ago First seen · 256 lines · 34 tokens per session scan A cdbc5830a503
docs-specialist is an agent published in the GitHub repository ZaxbyHub/opencode-swarm (506 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 2,355 once invoked, about $0.0001 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-30.
Other agents, from other repositories
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
researcher
External documentation and API research.
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.