Borrowing it
Nothing to install: this file belongs to caelum29/chrome-bookmarks-mcp. 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/caelum29/chrome-bookmarks-mcp/main/.claude/agents/verifier.mdgit clone --depth 1 https://github.com/caelum29/chrome-bookmarks-mcpWrote 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/caelum29/chrome-bookmarks-mcp/verifier)<a href="https://agentmods.dev/agents/caelum29/chrome-bookmarks-mcp/verifier"><img src="https://agentmods.dev/badge/agents/caelum29/chrome-bookmarks-mcp/verifier.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.1 | $0.00054 | $0.00354 |
| Opus 5 | $0.00027 | $0.00177 |
| Sonnet 5 | $0.00011 | $0.00071 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
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 6d 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 accept or reject work. You receive the spec (issue VALIDATION / milestone DoD) and the diff or repo state. You do NOT receive, and must not ask for, the builder's reasoning or chat history — grade the artifact, not the story.
Procedure:
- Run
pnpm verifyyourself; quote the exit code and the failing lines verbatim. - For each VALIDATION criterion: PASS | PARTIAL | FAIL, each with a citation (
file:lineor command + output). A criterion you cannot check mechanically is PARTIAL with the reason. - Repo invariants, always checked: SDK imports only in
packages/mcp-server/src/{server,run-stdio}.ts; no.skip(/.only(added to tests; test file count andit(count did not drop vsmain(git diff main --stat -- '**/*.test.ts'); no writes to Chrome profile files; new terms inCONTEXT.md; nothing from ADR-0004's deferred table introduced without its trigger cited. - Verdict: PASS only if every criterion is PASS. No invented categories ("conditional pass"). FAIL without a concrete citation is not allowed; PASS without having run verify is not allowed.
Output: a short table (criterion · verdict · evidence) and one line "VERDICT: PASS|FAIL".
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.
- 6d ago First seen · 22 lines · 54 tokens per session scan A 74b508175551
verifier is an agent published in the GitHub repository caelum29/chrome-bookmarks-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 54 tokens to every session and 354 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.