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 instructions/joelhooks/swarm-tools/agents-mdgit clone --depth 1 https://github.com/joelhooks/swarm-toolsWrote 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/instructions/joelhooks/swarm-tools/agents-md)<a href="https://agentmods.dev/instructions/joelhooks/swarm-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/joelhooks/swarm-tools/agents-md.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.11102 | $0.11102 |
| Opus 5 | $0.05551 | $0.05551 |
| Sonnet 5 | $0.02220 | $0.02220 |
| Haiku 4.5 | $0.01110 | $0.01110 |
Grade C, and why
swarm-tools AGENTS.md 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.
rm -rf .turbo/cache The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 1,443 lines · 11,102 tokens per session scan C 80256db3a4ea
swarm-tools AGENTS.md is an instructions file published in the GitHub repository joelhooks/swarm-tools (733 stars, last pushed 1mo ago), with no licence file. It adds 11,102 tokens to every session, about $0.0555 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-30.
Other instructions, from other repositories
opencode-ensemble AGENTS.md
AGENTS.md instructions for hueyexe/opencode-ensemble, covering opencode-ensemble — agent guidelines, what this is, design context, users and brand personality.
solo AGENTS.md
Instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
Recall AGENTS.md
Instructions for samzong/Recall, covering agents.md, commands, architecture and boundaries.
opencode-hive AGENTS.md
Instructions for rretsiem/opencode-hive, covering opencode hive, directory structure, ai setup instructions, step 1: discover available models and step 2: detect target project stack.
marimo CLAUDE.md
Claude Code instructions for marimo-team/marimo, a project described as: A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
clankerchat AGENTS.md
Instructions for simozampa/clankerchat: Preserve changes you did not create. Keep edits small and use Conventional Commits without attribution trailers. Run npm run check before declaring work complete.