proofshot: Instructions file for Claude Code

CLAUDE.md

proofshot CLAUDE.md is an instructions file for Claude Code from AmElmo/proofshot. It costs 1,221 tokens per session, scanned A, original, MIT.

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 for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is AmElmo/proofshot's own configuration. It tells Claude Code how to work on proofshot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything proofshot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to AmElmo/proofshot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AmElmo/proofshot/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/AmElmo/proofshot

Made for: Claude Code.

Wrote 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.

agentmods badge for proofshot CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/amelmo/proofshot/claude-md/github.svg)](https://agentmods.dev/instructions/amelmo/proofshot/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/amelmo/proofshot/claude-md"><img src="https://agentmods.dev/badge/instructions/amelmo/proofshot/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for proofshot CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/amelmo/proofshot/claude-md"><img src="https://agentmods.dev/badge/instructions/amelmo/proofshot/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01221 $0.01221
Opus 5.5 $0.00488 $0.00488
Sonnet 5.5 $0.00244 $0.00244
Haiku 4.5 $0.00122 $0.00122

Measured 2mo ago against content hash 5c9fadca2552, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.ts → src/cli.ts → src/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 state — start writes .session.json, exec and stop read it. stop clears it. Don't assume session exists without checking
  • Session metadata — start 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. 2mo 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 (870 stars, last pushed 6mo ago), licensed MIT. It adds 1,221 tokens to every session, about $0.0049 per session on Opus 5.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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens