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-specgit 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-spec)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-spec"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-spec.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.00091 | $0.01255 |
| Opus 5 | $0.00046 | $0.00628 |
| Sonnet 5 | $0.00018 | $0.00251 |
| Haiku 4.5 | $0.00009 | $0.00126 |
Grade A, and why
swarm-spec 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-spec — requirements phase
Quality here is leverage: every later phase builds on this document. Expect the strongest available model — if this session runs a lesser tier, say so and let the user decide.
Pick a planning mode first
Requirements work isn't an interrogation — the goal is to remove confusion and unstated assumptions, not to make the user answer a hundred questions. Before diving in, offer how much to involve them (recommend hybrid; they can switch anytime):
- ask-each — put every genuinely uncertain requirement to the user before locking it. Maximum control, slowest.
- recommend-all — proceed on your recommendations/assumptions for all features, record each assumption, and surface them together for one batch review. Fastest.
- hybrid (default) — ask on the high-stakes or truly ambiguous decisions; assume sensible defaults on the rest and log them. The user may also scope it ("ask me about auth and billing, assume the rest").
Whatever the mode, every assumption is recorded (in the question queue, status ASSUMED)
so the closing summary can show exactly what you decided for them.
Clarify, don't grill
Only decisions go to the user; facts are looked up (codebase, vault, web). For each decision surfaced: lead with a recommendation, state the assumption behind it, list the alternatives, and accept any free-text answer. If something is only mildly uncertain and the mode allows, assume the sensible default and note it rather than asking.
The question queue — 30 Plans/<P>/question-queue.md (machine lane) — keeps a long
conversation honest across sessions and compaction:
- Every item gets an ID + status:
OPEN / ASKED / ANSWERED / ASSUMED / PARTIAL / PARKED. - An answer that resolves other items: cross-mark them with the answer's ID.
- The user changes topic or adds a requirement mid-stream: APPEND a new branch; the main track is never dropped. Return to open items before the phase can complete.
- Re-read the queue on resume — it, not the transcript, is the memory.
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.
- 6d ago First seen · 96 lines · 91 tokens per session scan A cd9650b5fb1d
swarm-spec is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,255 once invoked, about $0.0005 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-31.
Other skills, from other repositories
architect-review
use when user ask to review spec.
data-integrity-review
Data integrity specialist for schema correctness, owner isolation, projections, hash chains, log separation, snapshots, and replay consistency. Use when validating that data remains correct under sync and persistence rules.
coder
Use when the task is to implement code changes from an assigned scope, including bug fixes, follow-ups, rejects, or current-worktree repair.
skill-creator
Use when the user asks to create or update a skill.
ui-be-binding-skill
Use when binding backend/API data into an already-approved frontend UI without changing approved layout, copy, visual design, component hierarchy, or interaction states.
planner
Use when the user asks to create, write, or review a docs/plans plan.