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/amelmo/proofshot/claude-mdgit clone --depth 1 https://github.com/AmElmo/proofshotWhat 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.01221 | $0.01221 |
| Opus 5 | $0.00611 | $0.00611 |
| Sonnet 5 | $0.00244 | $0.00244 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
proofshot CLAUDE.md scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **agent-browser** — external peer dependency (Rust CLI + Node daemon). All browser commands go through `ab()` in `utils/exec.ts` which calls `agent-browser <command>` via `execSync` How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProofShot CLI
Visual verification tool for AI coding agents. Records browser sessions, captures screenshots, collects errors, and bundles proof artifacts.
Quick reference
npm run build # Build with tsup (must run after changes)
npm test # Run vitest once
npm run dev # Watch mode build
Architecture
src/
├── cli.ts # Commander.js command registration
├── commands/ # One file per CLI command (install, start, stop, exec, diff, pr, clean)
├── browser/ # agent-browser CLI wrappers (session, capture, interact, navigate)
├── server/ # Dev server detection, startup, port waiting
├── session/state.ts # .session.json lifecycle (save/load/clear)
├── session/metadata.ts # Persistent per-session metadata (branch, commit) for PR matching
├── artifacts/ # Output generation (viewer.html, SUMMARY.md, PR format)
└── utils/ # Config, exec helpers, port utils, error patterns, GitHub API
Entry point: bin/proofshot.ts → src/cli.ts → src/commands/*.ts
Key conventions
- ESM only — all imports MUST use
.jsextensions:import { foo } from '../utils/config.js' - Build before test — CLI runs from
dist/, alwaysnpm run buildafter code changes - agent-browser — external peer dependency (Rust CLI + Node daemon). All browser commands go through
ab()inutils/exec.tswhich callsagent-browser <command>viaexecSync - Session state —
startwrites.session.json,execandstopread it.stopclears it. Don't assume session exists without checking - Session metadata —
startwritesmetadata.jsoninside each session folder with git branch/commit. This persists afterstopand is used byprto match sessions to branches - Per-session subfolders — artifacts go in
proofshot-artifacts/YYYY-MM-DD_HH-mm-ss_slug/
Command lifecycle
proofshot start— spawns dev server, opens browser, starts recording, saves session state + writesmetadata.jsonwith git branch/commitproofshot exec <args>— logs action tosession-log.json, forwards toagent-browserproofshot stop— collects errors, stops recording, trims video, generates SUMMARY.md + viewer.html, clears sessionproofshot pr [number]— finds sessions for current branch, uploads artifacts to GitHub, posts PR comment
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 · 96 lines · 1,221 tokens per session scan A 5c9fadca2552
proofshot CLAUDE.md is an instructions file published in the GitHub repository AmElmo/proofshot (855 stars, last pushed 4mo ago), licensed MIT. It adds 1,221 tokens to every session, about $0.0061 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
Browser4 CLAUDE.md
Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.
spring-ai-agentcore AGENTS.md
Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
fast-browser CLAUDE.md
Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.
agentoscope AGENTS.md
Instructions for rafaelcg/agentoscope, covering agentoscope — agent instructions, what this is, layout, commands and conventions.