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-ejectnpx skills add AnmarHani/SwarmVault --skill swarm-ejectgit 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-eject)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-eject"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-eject.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 | $0.00072 | $0.00861 |
| Opus 5 | $0.00036 | $0.00430 |
| Sonnet 5 | $0.00014 | $0.00172 |
| Haiku 4.5 | $0.00007 | $0.00086 |
Grade C, and why
swarm-eject scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Ejecting is not `rm -rf`. A project is wired in six places, and a partial removal leaves the How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-eject — leaving cleanly
Ejecting is not rm -rf. A project is wired in six places, and a partial removal leaves the
user worse off than never installing: a marker with no registry entry, instruction files
still pointing agents at a vault that no longer has the project, hooks firing into nothing.
The eject command does the work; this skill runs the conversation.
1. Ask which exit they want
Lead with the recommendation. Most people asking this want unwire, not deletion.
| mode | what happens to the knowledge | reversible |
|---|---|---|
| unwire (default, recommend first) | stays in the vault; the project just stops being wired | yes — register brings it back |
| export | copied into the repo at docs/swarmvault-archive/, then removed from the vault |
via those files |
| purge | deleted | only from the backup |
If they say something like "remove SwarmVault from this project," that is unwire unless they explicitly say delete. Ask before assuming otherwise.
2. Show the inventory before doing anything
The command's default is a dry run, so run it plainly and read the output back:
swarmvault.py eject --project <P> --mode unwire|export|purge
It prints what leaves and what stays: note counts per vault folder, total size, the exact
instruction files and hooks to be unwired, and — for export and purge — every inbound
[[wikilink]] from other projects that would go dead. Surface the orphan warning to the
user; it is the one consequence they cannot see coming.
3. Apply
swarmvault.py eject --project <P> --mode <mode> --apply [--backup PATH]
- purge asks for the project name typed back. Don't work around that prompt; if the
session is non-interactive, tell the user and let them pass
--confirm-name <P>. - A backup tarball is written outside the vault before any deletion.
--no-backupexists; don't reach for it, and never pass it on the user's behalf. - Report the printed log back rather than summarising it as "done."
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.
- 4d ago First seen · 79 lines · 72 tokens per session scan C 3f7004b95f87
swarm-eject is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 861 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
claude-to-deerflow
Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to…
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator.
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.
sprint-planning
Plan implementation sprints with story selection, goal definition, and execution ordering.