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-skill-forgegit 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-skill-forge)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-skill-forge"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-skill-forge.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.00045 | $0.00705 |
| Opus 5 | $0.00023 | $0.00352 |
| Sonnet 5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
swarm-skill-forge 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-skill-forge — skill authoring
A skill is packaged judgment: instructions a future agent follows instead of its defaults. Write one only when that trade is worth it.
Gate: should this be a skill?
- Recurring task with a non-obvious right way → skill.
- Single fact or preference → memory note. Project convention → CLAUDE.md/AGENTS.md line.
- One-off → nothing. When in doubt, don't — catalogs rot.
- Overlap check first:
lsthe installed skills; if an existing skill covers 70% of the job, extend it instead of adding a sibling (two skills for one job = router confusion).
Structure
---
name: kebab-case-verb-or-domain
description: <what it does> + <every trigger phrasing a user might use>. The
description IS the router — write it for the model deciding whether to load.
---
# Name — one-line job
Gate / when NOT to use.
Numbered steps, imperative, each observable ("run X, expect Y").
Rules the defaults would get wrong.
Worked example (input → output).
- Platform-agnostic markdown only — it must read the same via Claude Code skills and a Codex AGENTS.md index.
- Portable on its own (NFR-C4): the folder must work when copied out alone, with no
vault, no
swarmvault.py, and no siblings installed. Name peer skills by what they add, never as a prerequisite, and give every vault-backed path a local fallback ("voice.mdin the vault, else.writing/voice.md"). Skills about the vault are the exception. Degrade, don't downgrade: write the vault path first and fullest, then the fallback. A skill weakened so a lone copy can satisfy it has failed this rule, not passed it. - Heavy reference material (> ~150 lines) →
references/*.md, loaded on demand; the SKILL.md tells the reader which reference to load when. - Machine-lane style for checklists/tables; prose where nuance matters.
Verify before shipping (skills are code — test them)
- Trigger dry-run: write 3 paraphrases of how a user would ask; does the description clearly fire for them — and clearly NOT fire for near-misses?
- Toy walk: execute the skill on a small real case; every step must be doable without information the skill forgot to mention.
- Altitude check: delete every line the model would do correctly anyway — a skill states only what defaults get wrong.
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 · 64 lines · 45 tokens per session scan A ad04f60405ab
swarm-skill-forge is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 705 once invoked, about $0.0002 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.