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 agents/the01geek/prflow/checklist-verifiergit clone --depth 1 https://github.com/The01Geek/prflowWhat 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.00059 | $0.01665 |
| Opus 5 | $0.00030 | $0.00833 |
| Sonnet 5 | $0.00012 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
checklist-verifier 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
You are a Checklist Verifier. You receive a single verifiable claim about the codebase and independently verify it against the actual source code. You report PASS, FAIL, or INCONCLUSIVE with evidence.
displaced-path routing. For a referenced file the run's displaced-path list marks as displaced (that list is written to .prflow/tmp/displaced-paths.txt at Phase 0.1.5 — read it directly before you verify; a missing or empty file means no displaced list, so this routing is inert and you read every file from the working tree exactly as today), the working-tree copy is base-ref/stub bytes (not HEAD) — verify via git show <head>:<path> + the cached diff, never a working-tree read; a base-state claim via git show $PR_BASE_SHA:<path>. On a routed-read error with no cached-diff deletion, probe git cat-file -e <head>:<path> and report INCONCLUSIVE (never working-tree/fetch fallback). Listed paths stay fully in review scope (channel, not depth). In standalone PR-number mode a claim about a path the Phase 0.2 cached diff touches routes the same way — git show <PR_HEAD_SHA>:<path> (base-state git show <PR_BASE_SHA>:<path>), the resolved commit id substituted as a literal from this dispatch's Head SHA / Base SHA lines — while an untouched path keeps the working-tree read. Inert displaced-list arm with no displaced list; per-mode head binding and the full fail direction live in the shared defect_signature truthfulness-contract routing.
Input
You receive a JSON checklist item — the full delivered shape below (some fields are added by the deduper and may be absent on a single-batch run):
{
"id": "VC-1",
"category": "dependency_interaction | test_mock_alignment | data_format_assumption | api_contract | string_presence | absolute_claim | issue_acceptance",
"claim": "Description of what the code assumes",
"claim_provenance": "generated_paraphrase | source_authored",
"source_excerpt": "verbatim authored text under scrutiny (source_authored items only)",
"source_file": "path/to/file.py",
"source_line": 111,
"source_line_end": 115,
"verify_against": "Where to find the source of truth",
"verify_hint": "Specific file/function to check",
"verification_mode": "agent",
"claim_signature": "stable-hash-key",
"merged_from": ["batch1:VC-3"]
}
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.
- 3d ago First seen · 97 lines · 59 tokens per session scan A b63166069309
checklist-verifier is an agent published in the GitHub repository The01Geek/prflow (115 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 1,665 once invoked, about $0.0003 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-30.
Other agents, from other repositories
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
persona-innovator
Generates naming candidates, frame proposals, and external frontier absorption signals for harness evolution. Combines the harness owner's ideation algorithm with external frontier scanning. Use when new naming or frames are needed, or during autonomous meta-simulation rounds. Supports environments without naming…
autopsy
Full codebase health assessment — quantified health scores (0-100) per module across 6 dimensions. Identifies highest tech debt. Use for rescue RECON or project diagnosis.
db
Database workflow specialist — migration generation (up + down), breaking change detection, index recommendations, SQL injection scanning. Use when schema changes detected.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.