Borrowing it
Nothing to install: this file belongs to tonydzi/agent-leash. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tonydzi/agent-leash/main/AGENTS.mdgit clone --depth 1 https://github.com/tonydzi/agent-leashWrote 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/tonydzi/agent-leash/agents-md)<a href="https://agentmods.dev/instructions/tonydzi/agent-leash/agents-md"><img src="https://agentmods.dev/badge/instructions/tonydzi/agent-leash/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/tonydzi/agent-leash/agents-md"><img src="https://agentmods.dev/badge/instructions/tonydzi/agent-leash/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00834 | $0.00834 |
| Opus 5.5 | $0.00334 | $0.00334 |
| Sonnet 5.5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
agent-leash 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — working in this repo
Written for AI coding agents, and equally readable by a human contributor. Short on purpose.
What this repo is
LEASH-8: an 8-domain control model for AI agents that hold delegated authority. Patterns, not a product, and not our live control surfaces. There is no runnable code here — the deliverables are a scored worksheet, the control model, and two architecture notes.
If you are an agent reading this repo to apply it to your own operator's setup, start at
FOR-ROBOTS.md, then SCORECARD.md.
Layout
SCORECARD.md— 24 statements, scored 0/1/2, five minutes, produces a band.docs/leash-8.md— the eight domains, the minimal implementation of each, and what evidence to keep. The evidence column is the part that makes it auditable.docs/plan-vs-authorize.md— the core pattern: the model plans, a policy gate decides, an executor acts. Most of the repo is downstream of this separation.templates/approval-design-checklist.md— designing human approvals for irreversible actions.docs/a2a-agent-card.md+agent-card.json— reference A2A Agent Card.
How to verify a change
Nothing executes, except one file: agent-card.json must stay valid JSON and conform to the A2A
Agent Card shape described in docs/a2a-agent-card.md.
python -c "import json;json.load(open('agent-card.json'));print('agent-card.json OK')"
For everything else, verification is claim discipline (below). In the PR, say which claims you added or changed and what backs each one.
Conventions — the claim discipline
This repo's credibility is its only asset, so the rule is explicit:
- We claim: these controls reduce blast radius, raise attacker cost, and make agent actions reviewable — and we can show the implemented control, what it covers, and what stays with a human.
- We do not claim: "your agents will be secure", "prompt injection is solved", or any outcome guarantee. A PR that adds a sentence of that shape gets rejected however well written it is.
- Every external fact carries a source. Incident references, CVEs, benchmark results: link them, date them, and say what they do not show. A number without a source is the one defect that cannot be patched later — by then it has been quoted.
- Scoring must stay honest. If you change
SCORECARD.md, do not make a statement easier to score 2 on. The worksheet is useless the moment it flatters the reader. - No live control surfaces, no real infrastructure detail, no secrets. Patterns only.
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.
- 1mo ago First seen · 67 lines · 834 tokens per session scan A b29deba0fe4b
agent-leash AGENTS.md is an instructions file published in the GitHub repository tonydzi/agent-leash (5 stars, last pushed 18d ago), licensed MIT. It adds 834 tokens to every session, about $0.0033 per session on Opus 5.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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.