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/bolnet/attestor/claude-mdgit clone --depth 1 https://github.com/bolnet/attestorWrote 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/bolnet/attestor/claude-md)<a href="https://agentmods.dev/instructions/bolnet/attestor/claude-md"><img src="https://agentmods.dev/badge/instructions/bolnet/attestor/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.02293 | $0.02293 |
| Opus 5 | $0.01146 | $0.01146 |
| Sonnet 5 | $0.00459 | $0.00459 |
| Haiku 4.5 | $0.00229 | $0.00229 |
Grade A, and why
attestor 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attestor
The memory layer for agent teams. Self-hosted, deterministic retrieval, zero LLM in the critical path.
PyPI: attestor -- Python import: attestor.
Project Structure
attestor/
core.py -- AgentMemory class (main public API)
client.py -- MemoryClient (HTTP drop-in for remote Attestor)
context.py -- AgentContext (identity, role, namespace, token budget, provenance)
models.py -- Memory, RetrievalResult dataclasses
cli.py -- CLI entry point
api.py -- Starlette ASGI REST API
store/
base.py -- DocumentStore / VectorStore / GraphStore interfaces
registry.py -- Backend selection; default = postgres + neo4j
connection.py -- Config layering / env resolution
embeddings.py -- Provider auto-detect (local / OpenAI / Bedrock / Vertex / Azure)
postgres_backend.py-- Postgres (document role; pgvector embedding column kept in schema)
pinecone_backend.py-- Pinecone (vector role; auto-detects Local Docker vs Cloud)
neo4j_backend.py -- Neo4j + GDS (graph role, PageRank / BFS)
schema.sql
graph/
extractor.py -- Entity/relation extraction (4-output GraphRAG)
retrieval/
orchestrator.py -- 6-step semantic-first cascade (vector → BM25 → RRF → graph → MMR → fit)
tag_matcher.py
scorer.py -- Temporal + entity + PageRank boosts, confidence decay, MMR
temporal/
manager.py -- Contradiction detection, supersession, timeline, as_of replay
extraction/ -- Rule-based + optional LLM memory extraction
mcp/
server.py -- MCP server (tools + resources + prompts)
hooks/
session_start.py -- Context injection at session start
post_tool_use.py -- Auto-capture from Write/Edit/Bash
stop.py -- Session summary on exit
utils/
config.py, tokens.py
infra/local/ -- Docker Compose for local Postgres + Pinecone Local + Neo4j
tests/ -- Unit tests (live integration tests env-gated)
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.
- 5d ago First seen · 126 lines · 2,293 tokens per session scan A 307422f7ab2b
attestor CLAUDE.md is an instructions file published in the GitHub repository bolnet/attestor (14 stars, last pushed 3mo ago), licensed MIT. It adds 2,293 tokens to every session, about $0.0115 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
ratel AGENTS.md
AGENTS.md instructions for ratel-ai/ratel, covering agents.md — working in the ratel repo, build & test, rust, ts and python (from src/sdk/python/; needs uv).
OpenKB AGENTS.md
AGENTS.md instructions for VectifyAI/OpenKB, covering agents.md — openkb map for coding agents, read next, dev commands, module map (openkb/) and hard invariants.
mastra AGENTS.md
AGENTS.md instructions for mastra-ai/mastra: Unless asked, don't inspect reference or modify examples. Use the most-specific AGENTS.md; for package work, read packages/ /AGENTS.md first.
ACCESSIBILITY.md AGENTS.md
AGENTS.md instructions for mgifford/ACCESSIBILITY.md, covering repository instructions for ai coding agents, scope, when each instruction file is useful, project mission and status and required project context.
mesh-llm AGENTS.md
AGENTS.md instructions for Mesh-LLM/mesh-llm, covering agent notes, repo overview, key docs, public website and building.
Assistant CLAUDE.md
Claude Code instructions for bearlike/Assistant, covering agents guide — mewbo, mandatory: hydrate before touching files, what mewbo is, monorepo layering — read before adding a module and engineering principles.