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/kairyou/agent-tools/agents-mdgit clone --depth 1 https://github.com/kairyou/agent-toolsWhat 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.00564 | $0.00564 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
agent-tools 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
Conventions this repo has settled on. They live here because they cannot be inferred from the code, and getting them wrong costs a round of rework.
Build and test
Tests exercise the bundles in dist/, so run npm run build before npm test
after touching anything under capabilities/.
Layout
- Self-contained capabilities that work when copied by a Skill installer live
in
skills/. They may bundlescripts/,references/, andassets/in the same Skill directory. - Skills centered on a specific external or business system live in
skills/systems/. - Capabilities that require independent installation, hooks, shared runtimes,
generated bundles, or Agent configuration live in
capabilities/<capability>/, with per-agent adapters named<agent>-<form>.mjs. - Every executable installed into
~/.agent-toolsby the capability installer comes fromdist/; sources stay incapabilities/. Bundled scripts inside a self-contained Skill are installed with that Skill instead. - Capability-owned Skill templates that contain unrendered
{{TOKENS}}live incapabilities/<capability>/skills/and must not ship throughnpx skills add.config.default.jsoncremains the installer-merged exception from the repo root.
Settled decisions
- No migration or legacy-compat code. Breaking a layout is fine: bump a minor version and state the one-time manual cleanup in the summary.
- Add no new env knobs for timing: a value that follows from the caller's shape
belongs in a module constant, with a comment explaining that number. The
overrides already in
codex-hook.mjsandclaude-statusline.mjspredate this and stay unless a change removes them deliberately. - Never claim compatibility that has not been verified against a real gateway.
- Usage output lines carry no branding prefix; each display surface adds its own context.
Docs
- Never use CJK/fullwidth punctuation. Write
,.:;()even in Chinese text. In- term — descriptionlines the separator is—, not-. README.md,README.zh-CN.md, and bothdocs/trees change together.- Prefer deleting a sentence over explaining it. Say what the reader must do, not how it works inside.
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.
- 3d ago First seen · 54 lines · 564 tokens per session scan A 9c2fd0e3008f
agent-tools AGENTS.md is an instructions file published in the GitHub repository kairyou/agent-tools (172 stars, last pushed 5d ago), licensed MIT. It adds 564 tokens to every session, about $0.0028 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
plannotator AGENTS.md
AGENTS.md instructions for backnotprop/plannotator, covering plannotator, project structure, server runtimes, installation and environment variables.
golembot CLAUDE.md
Instructions for 0xranx/golembot, covering golembot — project conventions for claude code, architecture hard constraints, things you must never do, interface change rules and file responsibility boundaries.
solo AGENTS.md
Instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
OpenCode-GraphAgent CLAUDE.md
Instructions for LeXwDeX/OpenCode-GraphAgent, covering claude.md, what this is, commands, quality gates and build & codegen.
superset CLAUDE.md
Claude Code instructions for superset-sh/superset, a project described as: Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
awesome-copilot-id AGENTS.md
Instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.