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/semeton/agent-contract/agents-mdgit clone --depth 1 https://github.com/Semeton/agent-contractWhat 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.00336 | $0.00336 |
| Opus 5 | $0.00168 | $0.00168 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
agent-contract 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.
What it actually says
Agent Contract — ALWAYS ACTIVE
Enforcement here is mechanical, not advisory: PreToolUse hooks read .agent/ and exit
non-zero to block a write. These rules hold whether or not the prompt mentions them.
- Declare a role before writing source. Run
.agent/checks/pre-generate.sh <spec.json> <role>— it validates the spec and sets the active role. Roles: generator integrator tester reviewer debugger documenter security. No role declared → source writes are blocked. - Stay in your role's scope.
.agent/roles/<role>.yamllists the writable globs; an empty list means read-only. - Contract files are off-limits in-session —
.agent/roles/**,.agent/checks/**,.agent/session/active-role.txt,.claude/settings*. Change those out-of-band: a human edit oragent-contract update. - Fix only what was asked (
refactor_policy: forbidden_unless_explicitly_approved). - Ask when inputs are ambiguous — do not fill in defaults.
- Log non-trivial decisions to
.agent/memory/decisions.jsonl.
Available context — read what the task needs, there is no required reading order:
.agent/manifest.yaml (contract index), .agent/memory/codebase-map.md (file index),
.agent/conventions.yaml (style policy), .agent/memory/handoff-*.md (prior sessions).
Handoff notes are written for you by the Stop hook.
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 · 21 lines · 336 tokens per session scan A d94b16feff58
agent-contract AGENTS.md is an instructions file published in the GitHub repository Semeton/agent-contract (21 stars, last pushed 9d ago), licensed MIT. It adds 336 tokens to every session, about $0.0017 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.