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 AnmarHani/SwarmVault --skill swarm-designgit clone --depth 1 https://github.com/AnmarHani/SwarmVaultWrote 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/anmarhani/swarmvault/swarm-design)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-design"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-design/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/anmarhani/swarmvault/swarm-design"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-design.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.00055 | $0.00631 |
| Opus 5.5 | $0.00022 | $0.00252 |
| Sonnet 5.5 | $0.00011 | $0.00126 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
swarm-design 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-design — system design phase
Gate: requires a validated SRS (else route back to swarm-spec). Read the SRS and feature specs first; the design must answer them, not your habits.
Lane: this is the standard, agent-driven lane — you propose, the user validates. If the user wants to own the system rather than receive it (deep design, pseudocode, algorithm-level planning, "developer mode"), hand the phase to swarm-design-deep instead; the two replace each other and never run together.
Produce, in order
- Tech stack — options with trade-offs measured against the NFRs (not fashion), recommendation first; the user decides. Significant picks become ADRs.
- Decomposition — modules/services with single responsibilities, boundaries, and data flow. Prefer deep modules behind simple interfaces. Mermaid diagrams for the system view and any non-obvious flow.
- Data model & contracts — entities, relationships, API contracts where relevant.
- Cross-cutting strategy — error handling, logging, testing approach fit for the stack.
- Milestone boundaries — group FRs into build milestones; these become swarm-implement's ticket batches.
Rules
- Traceability table required: every Must-FR ↦ component; every NFR ↦ one line on how the design satisfies it. Nothing silently dropped.
- Options with recommendation for anything that meaningfully affects cost, lock-in, or complexity — never decide those silently (mode: in auto, only stack-level choices already delegated by the user proceed without asking; queue the rest).
- Simplicity doctrine: every moving part justifies itself; prefer known patterns (refactoring.guru names) over invention; when two designs both satisfy the NFRs, ship the smaller one.
- Each significant decision →
50 Decisions/<P>/ADR-NNN-<slug>.md(template:90 Templates/decision.md): context, options, decision, consequences, FR/NFR links.
Output & gate
docs/design.md (human lane) + ADRs, mirrored to the vault by sync. End with the user
validation gate (gated mode) or a self-check against the traceability table (auto mode);
update flow-state to phase: design-ui (if the SRS declares an interface) or
phase: tickets.
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 · 52 lines · 55 tokens per session scan A 580aaa844a6d
swarm-design is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 631 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
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect.