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/a16z/jolt/agents-mdgit clone --depth 1 https://github.com/a16z/joltWhat 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.00004 | $0.00004 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
jolt 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 2d 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.
This is a copy
100% identical to superpowers AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
CLAUDE.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.
- 2d ago First seen · 1 lines · 4 tokens per session scan A 6ebdb617a810
jolt AGENTS.md is an instructions file published in the GitHub repository a16z/jolt (1,020 stars, last pushed 2d ago), licensed Apache-2.0. It adds 4 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to superpowers AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
starknet.js AGENTS.md
Instructions for starknet-io/starknet.js, covering agents.md, setup & core commands, verifying your changes (read this before running tests), architecture map (src/) and conventions.
emilia-protocol AGENTS.md
Instructions for emiliaprotocol/emilia-protocol, covering repository instructions for ai agents, required first read, source discipline, context maintenance and verification.
emilia-protocol CLAUDE.md
Instructions for emiliaprotocol/emilia-protocol, covering emilia protocol - repo guide, required context, critical, build & ship and outbound & claims.
VCVio AGENTS.md
Instructions for Verified-zkEVM/VCVio, covering vcvio — ai agent guide, fast start, attribution, headers, and docstrings, module scopes and what this project is.
emilia-protocol copilot-instructions.md
Instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before proposing changes. Current evidence and provenance are in public/.well-known/emilia-context.json. Treat archived, staged, private, and outreach documents as non-authoritative for current behavior or standards status.
emilia-protocol GEMINI.md
Instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before analyzing or editing this repository. Use public/.well-known/emilia-context.json for current evidence counts and provenance. Do not infer current behavior or standards status from archived, staged, private, or randomly sampled…