proofshot CLAUDE.md

Repository instructions for ProofShot, a command-line tool that records browser sessions, takes screenshots, collects errors, and packages evidence of how a website works.

In plain words
What is it for?
Use them to build, test, and modify ProofShot commands, browser-session handling, development-server startup, saved session data, and generated proof reports.
Why use it?
They give a coding agent the project’s structure, commands, and rules, reducing mistakes when changing or checking the tool.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/amelmo/proofshot/claude-md
Clone the repo
git clone --depth 1 https://github.com/AmElmo/proofshot
Per session 1,221 This file is loaded in full into every session.
When invoked 1,221 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 5c9fadca2552, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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`
CLAUDE.md · 96 lines

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.tssrc/cli.tssrc/commands/*.ts

Key conventions

  • ESM only — all imports MUST use .js extensions: import { foo } from '../utils/config.js'
  • Build before test — CLI runs from dist/, always npm run build after code changes
  • 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
  • Session statestart writes .session.json, exec and stop read it. stop clears it. Don't assume session exists without checking
  • Session metadatastart writes metadata.json inside each session folder with git branch/commit. This persists after stop and is used by pr to match sessions to branches
  • Per-session subfolders — artifacts go in proofshot-artifacts/YYYY-MM-DD_HH-mm-ss_slug/

Command lifecycle

  1. proofshot start — spawns dev server, opens browser, starts recording, saves session state + writes metadata.json with git branch/commit
  2. proofshot exec <args> — logs action to session-log.json, forwards to agent-browser
  3. proofshot stop — collects errors, stops recording, trims video, generates SUMMARY.md + viewer.html, clears session
  4. proofshot pr [number] — finds sessions for current branch, uploads artifacts to GitHub, posts PR comment

Read the full file on GitHub · 96 lines

Changes

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.

  1. 2d ago First seen · 96 lines · 1,221 tokens per session scan A 5c9fadca2552

Subscribe to this mod's changes

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.