Borrowing it
Nothing to install: this file belongs to creatornader/atrib. 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/creatornader/atrib/main/CLAUDE.mdgit clone --depth 1 https://github.com/creatornader/atribWrote 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/creatornader/atrib/claude-md)<a href="https://agentmods.dev/instructions/creatornader/atrib/claude-md"><img src="https://agentmods.dev/badge/instructions/creatornader/atrib/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.
<a href="https://agentmods.dev/instructions/creatornader/atrib/claude-md"><img src="https://agentmods.dev/badge/instructions/creatornader/atrib/claude-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.20380 | $0.20380 |
| Opus 5.5 | $0.08152 | $0.08152 |
| Sonnet 5.5 | $0.04076 | $0.04076 |
| Haiku 4.5 | $0.02038 | $0.02038 |
Grade A, and why
atrib 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 4d 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
atrib: the protocol for verifiable agent actions
What this is
atrib makes the actions an AI agent takes provable. Every agent action becomes a signed, chain-linked record committed to a public Merkle log. Downstream consumers (the agent itself, merchants, auditors, other agents) can independently verify what happened without trusting any operator.
Product teams can put that record in the action path. A host can check an action before it runs, and later work can carry the signed context forward. atrib records tool calls (MCP via @atrib/mcp-wrap, framework-native via @atrib/agent or @atrib/openinference), transactions (six payment-related completion cases per the payments profile: ACP, UCP, x402, MPP, AP2, a2a-x402), and the agent's own intentional records and reads through the two cognitive verbs: attest (write: observation by default, annotation via ref.kind: "annotates", revision via ref.kind: "revises") and recall (read: shape-dispatched lookups, lineage walks, and handoff verification). The seven legacy primitive names (emit, atrib-annotate, atrib-revise, the recall_* family, trace, summarize, atrib-verify) stay mounted as permanent aliases over the same handlers per D164; records are byte-identical either way.
The same substrate supports agent recall, third-party audit, commerce settlement, handoffs, and controlled high-impact actions when a harness or runtime puts atrib records in the action path. atrib sits between identity (DIF/W3C) and payment or commerce surfaces (ACP/UCP/x402/MPP/AP2). It also makes post-hoc claims about agent activity provable.
When explaining the graph, keep the
D118
framing stable: atrib has one graph with two reading planes. The chronology
plane records event history and continuity. The declared-relationship plane
records signed claims about which records informed, anchored, annotated, or
revised other records. /v1/chain and /v1/trace are projections over that
graph, and the explorer primary trace path is a product presentation rule over
both projections.
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.
- 4d ago Changed · +53 tokens per session 9c2cfdaf9f08
- 11d ago Changed · +6 lines · +118 tokens per session badcb96a1ab6
- 12d ago Changed · +12 tokens per session 9b24f2fdaa3c
- 1mo ago Changed · -1 tokens per session 464e1729bd8e
- 1mo ago First seen · 434 lines · 20,198 tokens per session scan A bb4217ea4e31
atrib CLAUDE.md is an instructions file published in the GitHub repository creatornader/atrib (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20,380 tokens to every session, about $0.0815 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.