What is ai-incident-law CLAUDE.md?

A set of project instructions for an open, searchable collection of public cases where AI systems caused harm and led to legal or regulatory action.

Use it when working on the AI Incident Law single-page app, its JSON dataset, or its read-only Model Context Protocol server.

It gives coding agents the repository's purpose, technology choices, file layout, and working conventions in one place.

How snapsynapse/ai-incident-law configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/snapsynapse/ai-incident-law/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/snapsynapse/ai-incident-law

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/snapsynapse/ai-incident-law/claude-md/github.svg)](https://agentmods.dev/instructions/snapsynapse/ai-incident-law/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/snapsynapse/ai-incident-law/claude-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/ai-incident-law/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/snapsynapse/ai-incident-law/claude-md"><img src="https://agentmods.dev/badge/instructions/snapsynapse/ai-incident-law/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,556 This file is loaded in full into every session.

When invoked 1,556 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01556	$0.01556
Opus 5.5	$0.00622	$0.00622
Sonnet 5.5	$0.00311	$0.00311
Haiku 4.5	$0.00156	$0.00156

Measured 1mo ago against content hash ee629167e1e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ai-incident-law CLAUDE.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.

CLAUDE.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — AI Incident Law

Agent guidance for this repo. See AGENTS.md for the concise build-pipeline note; this file expands on it. Both are authoritative — keep them consistent.

Purpose

An open, searchable corpus of public matters where AI systems caused harm and drew legal or regulatory action (litigation, tribunal orders, agency actions). Ships as a standalone, dependency-free single-page app over a curated JSON dataset, queryable by both humans and agents. Part of the PAICE legal graph; implements the Obligation-First proceeding strand. Canonical site: https://aiincidentlaw.org/

Audience: compliance teams, legal counsel, AI governance leads, researchers.

Stack

Vanilla HTML/CSS/JS single-page app — no framework, no CDN, no API calls, no analytics, no browser storage.
Node.js (>= 20) is used only for maintainer tooling; there are no install-time dependencies in the shipped app.
Also published as an npm package (ai-incident-law) exposing a zero-dependency read-only MCP stdio server.

Directory layout

index.html — hand-edited SPA shell (safe to edit directly).
styles.css — local stylesheet.
app.js — local search, filtering, rendering.
data/data.json — source of truth for the dataset.
data.js — generated browser bundle (do NOT hand-edit).
api/v1/of/ — generated Obligation-First binding artifacts.
proceeding/, allegation/, determination/, authority/, party/, tombstone/ — generated Obligation-First record files. party/ is easy to miss when staging and breaks CI on its own; tombstone/ is currently empty.
scripts/ — maintainer tooling (build, validate, eval, MCP server, staleness report).
data/admission/ — the source-admission contract: the frozen legacy.json baseline, accepted receipts.json, and retained primary-source bytes under raw/.
ops/ — maintainer operating records (source admission, matter-monitor pilot, cross-repo mitigation queue, release evidence).
design/ — published provider observations and publication state.
handoffs/ — gitignored session-continuity queue. Never history: migrate anything durable and delete the file.
docs/ — data-schema.md, methodology.html, submit-a-case.html, legal-graph.html.
.well-known/ — MCP discovery + GuideCheck assistant guide.
agents.json, robots.txt, llms.txt, mcp.json, server.json — agent/MCP discovery metadata.
tests/ — MCP server + discovery Node tests.
.github/workflows/validate.yml — CI.

Read the full file on GitHub · 91 lines

Changes

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 · +31 lines · +525 tokens per session ee629167e1e9
2mo ago First seen · 60 lines · 1,031 tokens per session scan A 9386744e391e

Subscribe to this mod's changes

ai-incident-law CLAUDE.md is an instructions file published in the GitHub repository snapsynapse/ai-incident-law (0 stars, last pushed 2d ago), licensed MIT. It adds 1,556 tokens to every session, about $0.0062 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 Safety ai-governance ai-incident ai-law ai-regulation compliance

ai-incident-law CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ai-incident-law CLAUDE.mdsnapsynapse/ai-incident-law	Instructions file	0	2d ago	MIT	A	1,556	Claude Code
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

ai-incident-law: Instructions file for Claude Code