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-implementgit 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-implement)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-implement"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-implement/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-implement"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-implement.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.00069 | $0.01865 |
| Opus 5.5 | $0.00028 | $0.00746 |
| Sonnet 5.5 | $0.00014 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
swarm-implement 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-implement — implementation phase
Two roles. Check flow-state: no tickets yet → you're the planner; tickets exist → you're a worker.
Planner (strong model, once per milestone batch)
Gate: validated design. Read docs/design.md and the milestone's FR specs.
- Emit tickets to
30 Plans/<P>/tickets/TK-NNN-<slug>.md(template:90 Templates/ticket.md, machine lane): FR-ID trace,requires:edges (tracer-bullet order: thinnest end-to-end slice first), suggestedtier(size) andkind(design/planning/coding/review/docs— lets orchestration route the right model), DoD checklist, and CONTEXT — the exact notes/design sections a worker needs (nothing more). Also name the layers.requires:orders tickets that exist; it cannot say whether the thing being ordered exists at all. Two tickets were once written as if a persistence layer were there — the engine belonged to one ticket, the tables to another, and the carrier between them to nobody, so both DoDs were unreachable as written and the gap was findable only by grepping for a repository and finding none. So every ticket carries:provides:— the layers this ticket makes exist (ledger repository,recurrence tables)needs:— the layers it builds on, in the same words Everyneeds:must match some ticket'sprovides:.boardprints a PLANNING GAPS section anddoctorfails theticket coveragecheck when one does not, when arequires:names a ticket that was never written, or when two tickets claim the same layer. Rundoctorbefore you hand the batch to workers — the gap is cheap now and a stalled worker later.
- Ask the user ONCE (skip in auto mode if already answered at SRS validation): parallelism appetite, and is a browser/test environment available for UI verification?
- Update flow-state (
phase: implement, ticket count) — J1: state first, work second.
Model tiers: top — architecture-touching, complex logic, tricky concurrency;
mid — standard features, refactors; small — boilerplate, docs, simple UI. Workers on
the wrong tier for a ticket should say so rather than proceed on hard tickets.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 115 lines · 69 tokens per session scan A 76b1bd112740
swarm-implement is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 1,865 once invoked, about $0.0003 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
agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator.
agent-multi-repo-swarm
Agent skill for multi-repo-swarm - invoke with $agent-multi-repo-swarm.
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.