Borrowing it
Nothing to install: this file belongs to searlsco/prove_it. 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/searlsco/prove_it/main/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/searlsco/prove_it/claude-md"><img src="https://agentmods.dev/badge/instructions/searlsco/prove_it/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.1 | $0.01381 | $0.01381 |
| Opus 5 | $0.00691 | $0.00691 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade B, and why
prove_it CLAUDE.md scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **`install`/`uninstall`** manage global hook registrations in `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prove_it Development Guide
Architecture
prove_it is a config-driven hook framework for Claude Code. It reads .claude/prove_it/config.json from a project directory and runs matching tasks when Claude Code fires lifecycle events (SessionStart, PreToolUse, Stop). It also dispatches git hooks (pre-commit, pre-push).
Key modules
cli.js—CLI entry point, commands: install, uninstall, init, deinit, doctor, monitor, hook, prefixlib/dispatcher/claude.js—Main dispatcher for Claude Code eventslib/dispatcher/git.js—Dispatcher for git hookslib/dispatcher/protocol.js—Output formatting for Claude Code hook APIlib/checks/script.js—Runs shell commands as taskslib/checks/agent.js—Runs AI agent reviewer taskslib/checks/env.js—Runs env tasks that inject environment variables via CLAUDE_ENV_FILElibexec/guard-config—Standalone script: blocks edits to prove_it config fileslibexec/briefing—Standalone script: renders session orientation on SessionStartlib/defaults.js—Single source of truth for config defaults (CONFIG_DEFAULTS,DEFAULT_MODELS,DEFAULT_ALLOWED_TOOLS)lib/config.js—Config loading, merging, andbuildConfig()for initlib/init.js—Project initialization, git hook shim managementlib/template.js—Template variable expansion for agent promptslib/globs.js—File matching, source detection, config path detectionlib/monitor.js—prove_it monitorCLI: tails session logs in human-readable format
Claude Code Hook API
- PreToolUse:
permissionDecisionvalid values are"allow","deny","ask"(insidehookSpecificOutput). Never use"block"or"approve"—Claude Code silently ignores them. - Stop: uses top-level
decision: "block"or"approve"(different schema from PreToolUse). - SessionStart: outputs JSON with
additionalContextand optionallysystemMessage. session_idis available in hook input for all events.
Testing
./script/test # lint + unit tests + integration tests (the verification oracle)
./script/test_fast # lint + unit tests only (runs on Stop hook)
npm run test:integration # integration tests
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.
- 7d ago First seen · 107 lines · 1,381 tokens per session scan B ccd5c6af6ab8
prove_it CLAUDE.md is an instructions file published in the GitHub repository searlsco/prove_it (199 stars, last pushed 4mo ago), licensed MIT. It adds 1,381 tokens to every session, about $0.0069 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.