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/mearman/agent-permissions/agents-mdgit clone --depth 1 https://github.com/Mearman/agent-permissionsWhat 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.00002 | $0.00002 |
| Opus 5 | $0.00001 | $0.00001 |
| Sonnet 5 | $0.00000 | $0.00000 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
agent-permissions 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.
This is a copy
100% identical to tensorlake AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
README.md
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 · 1 lines · 2 tokens per session scan A b33563055168
agent-permissions AGENTS.md is an instructions file published in the GitHub repository Mearman/agent-permissions (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 2 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tensorlake AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
cocoindex-code CLAUDE.md
Instructions for cocoindex-io/cocoindex-code, covering claude.md, build and test commands, architecture, process model and key layers.
pi-fabric AGENTS.md
Instructions for monotykamary/pi-fabric, covering agents.md, golden rule: build when done, before committing and commits.
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
AutoAgents AGENTS.md
Instructions for liquidos-ai/AutoAgents, covering autoagents repository guidelines, project structure & module organization, code quality, naming conventions and error handling.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
hatch3r CLAUDE.md
Instructions for hatch3r/hatch3r, covering hatch3r — development instructions, architecture, development commands, two-axis pillar framework (2.0.0) and orchestrator self-discipline (bypass protection).