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/catfish-1234/proctor/claude-mdgit clone --depth 1 https://github.com/catfish-1234/proctorWrote 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/catfish-1234/proctor/claude-md)<a href="https://agentmods.dev/instructions/catfish-1234/proctor/claude-md"><img src="https://agentmods.dev/badge/instructions/catfish-1234/proctor/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 | $0.00872 | $0.00872 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
proctor CLAUDE.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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
proctor: project guide
What this is
proctor catches AI coding agents gaming their own test suites: deleting tests, skipping them,
weakening assertions, or hardcoding outputs to fake a green build. It ships as a CLI diff
analyzer, a git pre-commit hook, a Claude Code Stop hook, and a reproducible benchmark.
Want the deeper reasoning and architecture? See RESEARCH.md.
Rules for anyone (or anything) working in this repo
- Do not modify, skip, or delete tests to make them pass.
- If a test looks genuinely wrong, stop and flag it to a human with your reasoning. Don't quietly fix it yourself.
- A fix isn't done until the original, unaltered tests pass, or a human has explicitly approved a change to the test itself.
- Never hardcode an implementation value to match a test fixture literal.
- Never gut real logic behind a stub or an always-true mock.
These are the same rules proctor itself enforces on AI agents (see
src/skill/SKILL.md), applied to work on proctor's own codebase too.
Tech stack
- TypeScript, Node 20+, ESM
- tsup for the build, vitest for tests, commander for the CLI, picocolors for terminal output
parse-difffor git diff parsing- The deterministic core needs zero network.
--aiis an opt-in extra, never a requirement.
Project structure
src/
cli.ts # entrypoint, wires up every subcommand
types.ts # Verifier / Context / Finding / ProctorConfig shapes
engine.ts # runs the enabled verifiers, aggregates findings
diff.ts # git diff parsing
pre-classifier.ts # rejects binary/mode-only/rename-only/submodule/combined diffs before analysis
rules.ts # RULE_METADATA: name, description, and severity for every check ID
brand.ts # name and color tokens shared by CLI output and badges
receipt.ts # builds the "honest pass" / "caught" Receipt from findings
context/ # builds Context: discovers the diff, test globs, config, etc.
verifiers/ # one file per check, RH001 through RH013, pure functions
reporters/ # pretty.ts, json.ts, sarif.ts, markdown.ts, score.ts output formats
hooks/ # git pre-commit hook and Claude Code Stop hook
skill/SKILL.md # the canonical honest-completion ruleset agents follow
adapters/ # deploys SKILL.md to each supported agent, plus drift-check
badge/ # honest-pass badge generation
ai/ # optional AI judge, only touched when --ai is passed
bench/ # benchmark harness. Bundled into dist/cli.js like everything else in
# src/, but the task corpus it reads lives in the repo's own bench/
# directory and is NOT in the npm tarball, so `proctor bench` only
# works from a clone.
fixtures/ # planted true-positive and near-miss cases, one set per check
tests/ # mirrors src/, one test file per module
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.
- 4d ago First seen · 70 lines · 872 tokens per session scan A 484632435b78
proctor CLAUDE.md is an instructions file published in the GitHub repository catfish-1234/proctor (1 stars, last pushed 2d ago), licensed MIT. It adds 872 tokens to every session, about $0.0044 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-31.
Other instructions, from other repositories
domscribe CLAUDE.md
Instructions for patchorbit/domscribe, covering claude.md, what is domscribe?, how to work on this codebase, commands and install dependencies (pnpm, not npm).
ai-plugin GEMINI.md
Gemini CLI instructions for PostHog/ai-plugin, covering posthog extension, available tool categories and guidelines.
notfair-plugin CLAUDE.md
Claude Code instructions for nowork-studio/notfair-plugin, covering engineering execution standard, agent entry points (single sources of truth), working style: brutal honesty, relentless quality, repository purpose and critical: this ships to users.
writing-skills AGENTS.md
AGENTS.md instructions for surendranb/writing-skills, covering agents.md — writing-skills, what this is, layout, the skill anatomy contract (enforced by ci) and working here.
agent-skills GEMINI.md
Gemini CLI instructions for motherduckdb/agent-skills, covering motherduck skills for gemini cli, default routing, skill catalog, utility and workflow.
gambit GEMINI.md
Instructions for felipecabargas/gambit, covering gambit, skills, core, discovery and communication.