Borrowing it
Nothing to install: this file belongs to binary16labs/prime-silo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/binary16labs/prime-silo/main/.claude/agents/board-verifier.mdgit clone --depth 1 https://github.com/binary16labs/prime-siloWrote 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/agents/binary16labs/prime-silo/board-verifier)<a href="https://agentmods.dev/agents/binary16labs/prime-silo/board-verifier"><img src="https://agentmods.dev/badge/agents/binary16labs/prime-silo/board-verifier/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.
<a href="https://agentmods.dev/agents/binary16labs/prime-silo/board-verifier"><img src="https://agentmods.dev/badge/agents/binary16labs/prime-silo/board-verifier.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.00444 |
| Opus 5.5 | $0.00022 | $0.00178 |
| Sonnet 5.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 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.
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.
- 2mo 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 13d ago), licensed MIT. It adds 56 tokens to every session and 444 once invoked, about $0.0002 per session on Opus 5.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.
board-verifier compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| board-verifierbinary16labs/prime-silo | Agent | 5 | 13d ago | MIT | A | 56 | Claude Code |
| sverklo-exploresverklo/sverklo | Agent | 82 | 2mo ago | MIT | A | 96 | Claude Code |
| bank-extractledq/resumery | Agent | 2 | 1mo ago | MIT | A | 91 | Claude Code |
| Patronus Securitytenable/cyberagents-exchange | Agent | 23 | yesterday | none | A | 27 | Claude Code |
| 888-apexariffazil/AAA | Agent | 0 | 5d ago | AGPL-3.0 | A | 77 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | 4d ago | MIT | A | 33 | Claude Code |