Borrowing it
Nothing to install: this file belongs to snapsynapse/ai-incident-law. 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/snapsynapse/ai-incident-law/main/AGENTS.mdgit clone --depth 1 https://github.com/snapsynapse/ai-incident-lawWrote 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/snapsynapse/ai-incident-law/agents-md)<a href="https://agentmods.dev/instructions/snapsynapse/ai-incident-law/agents-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/ai-incident-law/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/snapsynapse/ai-incident-law/agents-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/ai-incident-law/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.00429 | $0.00429 |
| Opus 5.5 | $0.00172 | $0.00172 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
ai-incident-law 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.
What it actually says
AI Incident Law — agent instructions
Build pipeline
index.html is hand-edited (the SPA shell). No script writes it. Safe to edit directly.
Generated files in this repo:
data.js— produced byscripts/build-data.mjsfromdata/data.json. Do NOT hand-edit.data/data.jsongenerated_atfield — derived at build time from newest recordlast_verified_date/last_checked_date. Do NOT hand-edit.api/v1/of/— Obligation-First binding artifacts produced byscripts/build-obligation-first.mjs.
Edit data/data.json records or index.html SPA shell directly. Then:
npm run build # build:data + build:of + validate:data
npm run check # the full gate; read the "check" script in package.json, it grows
Then stage the whole generated set. CI asserts generated artifacts are committed
(git diff --exit-code), so a data change that lands without its output fails the build:
git add data/ data.js api/ proceeding/ allegation/ determination/ authority/ party/ tombstone/ tests/fixtures/
party/ and tests/fixtures/of-contract-fingerprint.json are both easy to miss and both
break CI on their own. Add index.html only if the SPA shell was hand-edited. If a record's
jurisdiction changed, delete the stale authority/<old-slug>.json and
api/v1/of/records/<old-slug>.json before committing, or the generated set will not match
the data.
When in doubt, grep scripts/ for the file path before editing.
Cross-portfolio context
AI Incident Law is part of the PAICE legal graph. Implements the Obligation-First proceeding strand. Schema canon is at https://obligationfirst.org/. Portfolio canon at https://paice.foundation/ (~/Git/paice-foundation/INTENT.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.
- 1mo ago Changed · +12 lines · +159 tokens per session ceec0432e6fa
- 2mo ago First seen · 26 lines · 270 tokens per session scan A 6d0396b1bf32
ai-incident-law AGENTS.md is an instructions file published in the GitHub repository snapsynapse/ai-incident-law (0 stars, last pushed 2d ago), licensed MIT. It adds 429 tokens to every session, about $0.0017 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.
ai-incident-law AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ai-incident-law AGENTS.mdsnapsynapse/ai-incident-law | Instructions file | 0 | 2d ago | MIT | A | 429 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | yesterday | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |