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/kotobuki09/instructree/agents-mdgit clone --depth 1 https://github.com/kotobuki09/instructreeWhat 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.00087 | $0.00087 |
| Opus 5 | $0.00044 | $0.00044 |
| Sonnet 5 | $0.00017 | $0.00017 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
instructree 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 yesterday.
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
Contributor instructions
- Keep Instructree dependency-free at runtime.
- Use Node.js built-ins and support Node.js 20 or newer.
- Add or update a focused
node:testcase for every behavior change. - Preserve deterministic output: sort discovered paths and diagnostics.
- Describe heuristic findings as possible conflicts, never as proven agent behavior.
- Run
npm testandnpm run checkbefore submitting a change.
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.
- yesterday First seen · 9 lines · 87 tokens per session scan A fcb03346eaa9
instructree AGENTS.md is an instructions file published in the GitHub repository kotobuki09/instructree (0 stars, last pushed 6d ago), licensed MIT. It adds 87 tokens to every session, about $0.0004 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-31.
Other instructions, from other repositories
ai-agent-rules-generator copilot.instructions.md
Glitch WooCommerce Payment Gateway plugin coding guidelines — auto-doc sync for plugin, features, and infrastructure.
ai-agent-rules-generator agent-observations.instructions.md
Mandatory agent observation logging — anomalies, recommendations, and critical findings must be disclosed before commit.
ai-agent-rules-generator task.instructions.md
Task execution rules for Glitch WooCommerce Payment Gateway engineering work.
ai-agent-rules-generator doc-sync.instructions.md
Documentation sync rules — which docs to update when code changes.
ai-agent-rules-generator browsetools.instructions.md
Browser verification rules for Glitch WooCommerce Payment Gateway using Chrome DevTools MCP.
atelier AGENTS.md
Instructions for ahamedzoha/atelier, covering agents.md — the ai contract for this repo, 0. first contact — read this before your first reply, 1. the prime directive depends on the mode, 2. the three modes and guided (default).