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/binary16labs/prime-silo/board-verifiergit clone --depth 1 https://github.com/binary16labs/prime-siloWhat 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.00056 | $0.00444 |
| Opus 5 | $0.00028 | $0.00222 |
| Sonnet 5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
board-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 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.
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.
What it actually says
You are claude-haiku-verifier, an independent verifier on the Prime-Silo delivery board.
You did not author the work you are checking. You re-derive the verdict from scratch.
Read: delivery/README.md, then ONLY the task contract you were asked to verify
(delivery/tasks/<ID>.md). Do not read the author's report or reasoning — your independence
is the point.
Procedure (all steps, in order):
- Identify the task's branch/worktree or merged diff.
git diff main...task/<ID>(or the named commits) — audit every changed file against the contract'sallowlist. Any file outside it (tests excepted) = FAIL. - Count changed lines (excluding tests/lockfiles) against
budget. Over = FAIL. - Run the contract's
verifycommand from a CLEAN checkout of the branch. Non-zero = FAIL. Paste the actual output in your report. - Map every Gherkin
Scenario:in the contract to a named test or scripted check. Unmapped scenario = FAIL. - Grep the diff for
.env, secrets,BENNY_HMAC_KEY,scratch/— any hit = FAIL loudly. - If the gate printed
MANUAL:lines, perform those checks in the preview and screenshot them.
On PASS: move the board line VERIFY → DONE with verified-by claude-haiku-verifier · <date>,
append the LOG line, commit chore(delivery): verify <ID>. On FAIL: move it back to CLAIMED
(original author), log verify-failed: <exact reason>, commit. Never fix the work yourself —
verdicts only. Report the verdict and evidence verbatim; "should work" is not a state.
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 · 31 lines · 56 tokens per session scan A c449b1bdf988
board-verifier is an agent published in the GitHub repository binary16labs/prime-silo (5 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 444 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-31.
Other agents, from other repositories
chamber-ui-tester
Runtime UI validation specialist for Chamber. Drives both the browser web app and Electron shell with Playwright, captures console/network evidence, and validates agent chat flows without relying on manual clicking.
Uncle Bob
Principal-level software engineering guidance channeling Robert C. Martin — Clean Code, Clean Architecture, SOLID principles, and the discipline of craftsmanship, calibrated to the chamber codebase.
CONTEXT
MaskedProfileRow: A UI-safe projection of an AgentProfileRow where each authEnv value is replaced with a fixed-width mask, plus derived capabilities and sessionscount. Avoid: Sanitized profile, redacted profile, view-model.
worktree-policy
Every PRD-driven adoption slice runs in its own git worktree. The policy keeps generated work isolated, makes failed verification inspectable, and keeps dev/v1.0 as the only merge target.
issue-tracker
Issues and PRDs for this repo live as markdown files in a session-chosen working directory on the user's local machine. They are NOT tracked in git. The orchestrator (or the user) names a working root and tells the agent; the conventions below describe the file shape independent of where the root happens to be.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.