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-initgit 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-init)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-init"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-init/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-init"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-init.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.00060 | $0.00734 |
| Opus 5.5 | $0.00024 | $0.00294 |
| Sonnet 5.5 | $0.00012 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
swarm-init 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-init — new project onboarding
Idempotent: safe to re-run on an initialized project (repairs missing pieces, changes nothing else).
Steps
-
Vault exists?
swarmvault.py doctor. If no vault: offerswarmvault.py initfirst. Mention once: opening the vault folder in Obsidian gives the graph and backlinks — optional, never required (docs/obsidian-guide.md). -
Ask (only what is genuinely the user's):
- Project name (default: directory name).
- Isolation: shared (cross-project queries see it) or isolated?
- Which agentic platforms to wire — the tools they actually have (
claude-code,codex,gemini,opencode,droid,cursor,copilot,amp, or any other agent CLI by name), and global or per-project. - Git init, if no repo (recommended — the flow's traceability uses commits; optional).
- Optional orchestration for this project? Ask it as a pace — off / budget / balanced / fast — plus whether workers may edit code. Never ask for a worker count or a model name (swarm-orchestrate explains why) — but if they enable it, DO ask their plan and usage limits per platform: you cannot read those, and without them every usage number you print is invented.
- If not already set: make the vault the default for new projects? → save
"auto_init_new_projects": truein~/.swarmvault.json; future inits skip the ceremony.
-
Do it in one command — it registers, wires every named platform's own instruction file (plus Claude Code skills and hooks), syncs, and verifies:
swarmvault.py setup --platforms <list> --scope global|project \ [--name <name>] [--isolated] [--autonomy off|budget|balanced|fast] [--read-only]Already-registered project, or only need part of it?
register/wire --platforms …/sync --quiet/doctorare the same steps individually. Never leave the user manual file edits. -
Disclaimer (show once, verbatim):
SwarmVault stores project knowledge as plain files and runs local scripts. Auditing your environment, installed packages, and the data you place in the vault is your responsibility. Isolation flags are cooperative filtering between agents, not a security boundary.
-
Point forward:
/swarm-flowstarts the SDLC (first stop: swarm-spec).
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 · 59 lines · 60 tokens per session scan A 4e5903204e76
swarm-init is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 734 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
knowledge-curation
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.
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.