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/searlsco/prove_it/agents-mdgit clone --depth 1 https://github.com/searlsco/prove_itWrote 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/searlsco/prove_it/agents-md)<a href="https://agentmods.dev/instructions/searlsco/prove_it/agents-md"><img src="https://agentmods.dev/badge/instructions/searlsco/prove_it/agents-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.00545 | $0.00545 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
prove_it 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 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Testing
The problem
prove_it's hooks reference prove_it by name (e.g., $(prove_it prefix)/libexec/guard-config). When Claude Code fires hooks, the prove_it on PATH determines which version runs. During development, that's usually the Homebrew install—not your working tree.
The solution
script/agent launches Claude Code with test/bin/prove_it prepended to PATH. This shim resolves to the repo's cli.js, so every prove_it invocation—hooks, libexec scripts, transitive calls—uses your local source.
./script/agent # interactive
./script/agent -p "fix the bug" # with prompt
How it works
script/agent
└─ PATH="$REPO_ROOT/test/bin:$PATH" claude --dangerously-skip-permissions
└─ Claude Code fires SessionStart
└─ prove_it hook claude:SessionStart
└─ resolves to test/bin/prove_it → cli.js
└─ runs local-shim-check → confirms test/bin/prove_it is active
└─ records session baseline (lazy, internal)
All child processes inherit the modified PATH: hook dispatchers, libexec scripts, test scripts, agent reviewers.
Verification
The project's .claude/prove_it/config.json includes a local-shim-check as the first SessionStart task. On every session start, it runs:
which prove_it | grep -q test/bin/prove_it
- Pass:
prove_it resolves to local shim: .../test/bin/prove_it - Fail:
WARNING: prove_it resolves to /opt/homebrew/bin/prove_it, not test/bin/prove_it. Use ./script/agent to launch Claude with the local version.
This is a SessionStart task, so it warns but doesn't block—the agent sees the message and knows whether it's running against local source or the installed version.
When to use what
| Scenario | Command |
|---|---|
| Develop prove_it with live hooks | ./script/agent |
| Run tests from the CLI | ./script/test |
| Test a single hook manually | PATH="$(pwd)/test/bin:$PATH" prove_it hook claude:Stop <<< '{...}' |
| Test an example project | cd example/basic && PATH="../../test/bin:$PATH" claude |
| Use the installed (released) version | claude (normal) |
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 · 52 lines · 545 tokens per session scan A bff5cfdb8ca1
prove_it AGENTS.md is an instructions file published in the GitHub repository searlsco/prove_it (199 stars, last pushed 4mo ago), licensed MIT. It adds 545 tokens to every session, about $0.0027 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.