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/jrswab/axe/agents-mdgit clone --depth 1 https://github.com/jrswab/axeWrote 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/jrswab/axe/agents-md)<a href="https://agentmods.dev/instructions/jrswab/axe/agents-md"><img src="https://agentmods.dev/badge/instructions/jrswab/axe/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.03130 | $0.03130 |
| Opus 5 | $0.01565 | $0.01565 |
| Sonnet 5 | $0.00626 | $0.00626 |
| Haiku 4.5 | $0.00313 | $0.00313 |
Grade A, and why
axe 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 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.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Axe — AGENTS.md
What This Is
A lightweight CLI for running single-purpose LLM agents. Think make for AI — define agents in TOML, give them focused context via SKILL.md files, and trigger them from anywhere (cron, git hooks, pipes, file watchers).
Design Philosophy
- Small context windows by design. Each agent gets only what it needs. Sub-agents return results, not conversations. This is the core value prop — fight context bloat at every level.
- Unix citizen. Stdout is clean and pipeable. Debug goes to stderr. Exit codes are meaningful. Stdin is always accepted. Axe composes with existing tools, it doesn't replace them.
- Executor, not scheduler. Axe runs agents. Triggering is the user's job (cron, entr, git hooks, webhooks). No built-in daemon, no watch mode, no event loop.
- Single binary, zero runtime. Go. No interpreters, no node_modules, no Docker required.
go buildand ship. - Config over code. Agent definitions are TOML, not Go. Users should never touch source to define or modify agents.
Non-Obvious Constraints
- SKILL.md is a community format — not invented here. Treat it as an external standard. Don't add axe-specific extensions to the format itself; put axe-specific config in TOML.
- models.dev format for model strings — always
provider/model-name. Don't invent a custom format. - XDG Base Directory spec — config, data, and cache go where XDG says. No dotfiles in $HOME.
- Sub-agents are opaque to parents. A parent never sees a sub-agent's internal turns, tool calls, or files. Only the final text result crosses the boundary. This is intentional — don't leak internals upward.
- Depth limits are safety rails, not features. Default 3, hard max 5. If someone needs more depth, the design is wrong, not the limit.
What Good Contributions Look Like
- Tests for every new package (table-driven, no mocks when avoidable — use the real thing or
testutilhelpers) - Errors that help the user fix the problem, not just describe it
- No global state — pass dependencies explicitly
- Flags override TOML overrides defaults. Resolution order matters everywhere.
- When in doubt, print nothing. Axe output MUST be safe to pipe.
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 · 225 lines · 3,130 tokens per session scan A 69f19a570eca
axe AGENTS.md is an instructions file published in the GitHub repository jrswab/axe (836 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,130 tokens to every session, about $0.0157 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
ui-ux-pro-max-skill CLAUDE.md
Claude Code instructions for nextlevelbuilder/ui-ux-pro-max-skill, covering claude.md, project overview, search command, architecture and sync rules.
tweakcc AGENTS.md
AGENTS.md instructions for Piebald-AI/tweakcc, covering agents.md, development commands, build, testing and linting & formatting.
NeoHaskell AGENTS.md
AGENTS.md instructions for neohaskell/NeoHaskell, covering neohaskell — agent guide, hard rule, style (mandatory), commands (pointers, not a duplicate) and change flow (phase 5) — spec-gated, two human touchpoints.
tokf CLAUDE.md
Claude Code instructions for mpecan/tokf, covering tokf — development guidelines, project philosophy, commits, code quality and testing.
vue-tui AGENTS.md
AGENTS.md instructions for vuejs-ai/vue-tui, covering common pitfalls & best practices, project context records (pcr), using vite+, the unified toolchain for the web and review checklist.
repren AGENTS.md
Instructions for jlevy/repren, covering tbd and flowmark.