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/zaxbyhub/opencode-swarm/design-docsnpx skills add ZaxbyHub/opencode-swarm --skill design-docsgit 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/design-docs)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/design-docs"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/design-docs.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 | $0.00086 | $0.01497 |
| Opus 5 | $0.00043 | $0.00749 |
| Sonnet 5 | $0.00017 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00150 |
Grade A, and why
design-docs 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design-Doc Generation & Sync Protocol
Generate or maintain the project's structured design documentation. The work is delegated to the docs_design agent (a design-doc-author role variant of the docs agent). This mode authors a fixed set of version-controlled docs in the target project repo (NOT under .swarm/). It does NOT modify source code, does NOT call declare_scope, and does NOT touch .swarm/spec.md, CHANGELOG.md, or docs/releases/pending/*.
MODE: DESIGN_DOCS
Step 0 — Parse Header
Parse the [MODE: DESIGN_DOCS ...] header to extract:
out: output directory, project-relative (defaultdocs)lang: target language forreference/docs, orauto(defaultauto)update: boolean —true= sync existing docs to current code/spec;false= generate fresh- the trailing free text = the system description (required when
update=false)
If the header is malformed, report the error and stop.
Step 1 — Preconditions
- Confirm
design_docs.enabledis true (thedocs_designagent only exists when enabled). If it is not, tell the user to setdesign_docs.enabled: trueinopencode-swarm.jsonand stop. - If a spec-staleness block is active (
.swarm/spec-staleness.jsonpresent), resolve/acknowledge spec staleness FIRST — otherwise design-doc writes may be blocked by the guardrail, which emitsSPEC_DRIFT_BLOCK. Do not blindly retry onSPEC_DRIFT_BLOCK. - Read
.swarm/spec.mdif present — it is the authoritative requirements source (FR-### IDs). The design docs must be consistent with it. Run/swarm sdd statusto resolve the effective spec before reading.
Step 2 — Index Existing State (always)
Have the docs_design agent (or doc_scan) index <out>/ to discover any existing design docs. If <out>/reference/traceability.json exists, it is the section-ID registry — load it. Existing section IDs MUST be preserved on regeneration.
Step 3 — Generate or Sync
Dispatch the docs_design agent (the active swarm's docs_design — never the standard docs agent) with:
TASK,MODE(generate|sync),OUT_DIR,LANGUAGE- For sync:
FILES CHANGEDandCHANGES SUMMARYfrom the current phase/diff SKILLS: file:.swarm/bundled-skills/design-docs/SKILL.md(this skill)
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.
- 5d ago First seen · 84 lines · 86 tokens per session scan A 1deda69558f6
design-docs is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (464 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,497 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
ux-create-manifest
Create the initial Product UX Bible for an existing web or full-screen web app by deeply auditing the repository, using sub-agents when available, and generating docs/ux manifests, schemas, budgets, surface maps, action taxonomy, and design-token policies from observed code.
ux-principal
Principal UX architect skill for deciding WHERE a UI feature belongs, before it is implemented. Reads and maintains docs/ux manifests, classifies the feature, decides placement, navigation, surface, action hierarchy and complexity budgets, and produces a precise implementation brief without coding unless explicitly…
verify-changes
How to test and verify work in the dev-3.0 repo — which vitest config covers what, how to write a test that fits the house style, mocking Electrobun RPC and i18n providers, what coverage is actually expected, and the browser QA hand-off. Use when writing or fixing tests, deciding what a change needs covered, hitting a…
debug-ui
Drive and visually QA the dev-3.0 UI in a real browser (headless Chromium via agent-browser). Use when verifying a UI/UX change, reproducing a visual bug, taking screenshots of the running app, or self-QA before review. Triggers — "check the UI", "screenshot the app", "does this render", "QA this screen", "verify the…
gen-zhihu-article
Generate Zhihu article in the style of 22-庖丁解牛专题页-知乎图文终版.md.
zhihu-publish
Use when the task is to publish a Zhihu article from Markdown using the local browser-automation pipeline in this repo. Covers the text-only publishing chain, the multimodal chain that uploads Markdown images into the Zhihu editor, cookie-based login checks, and choosing between the stable text script and the richer…