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/creatornader/atrib/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.svg" alt="Measured on agentmods" 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 | $0.20198 | $0.20198 |
| Opus 5 | $0.10099 | $0.10099 |
| Sonnet 5 | $0.04040 | $0.04040 |
| Haiku 4.5 | $0.02020 | $0.02020 |
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 3d 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 — 434 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 protocols detected 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 rails (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.
- 3d 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 (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 20,198 tokens to every session, about $0.1010 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-31.
Other instructions, from other repositories
trustcard AGENTS.md
Instructions for davidnichols-ops/trustcard, covering trustcard — repo knowledge for agents, what this is, commands, architecture map (lib/) and entry points.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.