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/penberg/swarm/agents-mdgit clone --depth 1 https://github.com/penberg/swarmWhat 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.00109 | $0.00109 |
| Opus 5 | $0.00055 | $0.00055 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
swarm AGENTS.md 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 2d 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.
What it actually says
AGENTS
Coding Style
- Group imports so there is exactly one
useper crate. - For
std, prefer a single grouped import such asuse std::{...};instead of multipleuse std::...;lines. - Keep imports explicit and stable. Do not use wildcard imports.
- Follow the existing command layout:
- top-level CLI parsing in
opts.rs - command handlers in
cmd/ - storage and domain logic in top-level modules such as
repos.rs
- top-level CLI parsing in
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.
- 2d ago First seen · 12 lines · 109 tokens per session scan A dfdb9f458f63
swarm AGENTS.md is an instructions file published in the GitHub repository penberg/swarm (106 stars, last pushed 15d ago), licensed MIT. It adds 109 tokens to every session, 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-30.
Other instructions, from other repositories
herdr AGENTS.md
AGENTS.md instructions for herdrdev/herdr, covering herdr, scope and audience, universal project rules, principles and multiplicative performance paths.
kungfu AGENTS.md
AGENTS.md instructions for kungfu-systems/kungfu, covering agents.md, start from the person's objective, rules that always apply, load bounded context before changing the repository and execute and verify through shifu.
jarvis-registry AGENTS.md
AGENTS.md instructions for ascending-llc/jarvis-registry, covering jarvis registry — agent guide, project overview, ⚠️ plan mode instructions ⚠️, my engineering preferences and 1. architecture review.
kungfu CLAUDE.md
Claude Code instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before working in this repository. It routes both product use and contribution work to the repository sources of truth, including the requirement that development and build tasks enter through Shifu.
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
luvus AGENTS.md
Instructions for RizRiyz/luvus, covering agents.md, start with current evidence, product model, non-negotiable development safety and architecture and code map.