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/anmarhani/swarmvault/swarm-flownpx skills add AnmarHani/SwarmVault --skill swarm-flowgit 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-flow)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-flow"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-flow.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.01650 |
| Opus 5 | $0.00046 | $0.00825 |
| Sonnet 5 | $0.00018 | $0.00330 |
| Haiku 4.5 | $0.00009 | $0.00165 |
Grade A, and why
swarm-flow 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-flow — the SDLC router
Thin by design: this skill decides which phase runs; all expertise lives in the phase skills. Load the chosen skill before proceeding.
Read this before working, not after. In a SwarmVault-registered project this skill is the entry point for any substantive request — including ones that sound like a direct order ("add login", "fix the schema", "build the dashboard"). Route first, then work: two tool calls of routing prevent building the wrong thing, code with no ticket, or two agents editing the same file. If you are about to write feature code and cannot name the ticket it belongs to, you skipped this step — come back and route.
Deciding you can skip the flow is itself a flow decision. For genuinely trivial or one-off asks (a typo, a question about existing code, a shell one-liner) say so in one clause and proceed — but say it, so the user can disagree. Never skip silently.
The resume promise: routing needs ONLY vault state — flow-state, ticket statuses, the question queue, memory. "Continue project X" works from a cold session; never ask the user what happened last time, and never require a previous transcript. A session that died mid-work still lands correctly: stale claims surface via TTL, half-done phases surface via their artifacts.
Route
- Resolve the project (
swarmvault.py context .;doctorif that fails). - Read
30 Plans/<P>/flow-state.md— but artifacts on disk win over stale state; correct the note with a logged line if they disagree. - Decide by the first matching row:
| Observed state | Phase → skill |
|---|---|
| No SRS, no specs | requirements → swarm-spec |
SRS/specs draft or mined-draft |
validation pass → swarm-spec |
| SRS validated; no design doc | design → offer the lane choice below (+ swarm-design-ui if the SRS declares any user interface) |
| Designs validated; no tickets | ticket planning → swarm-implement |
| Open/claimed tickets | work the next unblocked ticket → swarm-implement |
| Milestone's tickets all done, no sweep report | milestone gate → swarm-review |
| Sweep findings open | fix tickets → swarm-implement |
| All milestones done | maintenance: bugs → swarm-debug; new asks → swarm-spec (change mgmt) |
| Any request whose deliverable is end-user-facing text | swarm-write (README, marketing, posts, UI copy, release notes) |
| User wants SwarmVault out of this project | offboarding → swarm-eject |
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 · 127 lines · 0 tokens per session scan A 09c612912c06
swarm-flow 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,650 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
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.
architect-review
use when user ask to review spec.
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.