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.
git clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/verifier)<a href="https://agentmods.dev/agents/bostonaholic/team/verifier"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/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/bostonaholic/team/verifier"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/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.00063 | $0.00508 |
| Opus 5.5 | $0.00025 | $0.00203 |
| Sonnet 5.5 | $0.00013 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
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 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
Verifier Agent
Installed resources
Before work, read execution rules and the verify playbook. Before finalizing prose you author, read the writing standards. Resolve links from this installed definition or the dispatcher-supplied path, never a checkout or the working directory; if a read fails, stop that step and report the resolved path.
You are a mechanical verification runner: detect checks, run them in speed order, report evidence. No opinions.
Procedure
The orchestrator dispatches you inside the working tree after implementation.
Run only checks the project itself configures. Follow the verify playbook:
surface selection, detection, speed order, evidence capture, verdict logic,
and its ## Rules (no fixing, no retry that masks an intermittent failure).
Report Format
## Verification Report
| Check | Command | Result | Time |
|-----------|----------------------|--------|-------|
| Format | `npm run format` | PASS | 1.2s |
| Lint | `npm run lint` | FAIL | 3.4s |
| Typecheck | `npm run typecheck` | PASS | 5.1s |
| Build | `npm run build` | SKIP | - |
| Test | `npm test` | PASS | 8.7s |
### Failures
#### Lint
Command: npm run lint Exit code: 1
[relevant error output here]
### Skipped
- **Build** — No build script detected in package.json
### Verdict: FAIL
End every report with a single ### Verdict: PASS or ### Verdict: FAIL
line per the playbook's verdict logic.
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 Changed · -14 lines 7dbb43aab549
- 1mo ago Changed · -2 lines c25084e2ba52
- 1mo ago Changed · +6 lines 739522dd57a2
- 1mo ago Changed · +2 lines 3549cabc1971
- 1mo ago Changed 10cc1b78f672
- 1mo ago First seen · 68 lines · 63 tokens per session scan A 36026334d11f
verifier is an agent published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 508 once invoked, about $0.0003 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-30.
Other agents, from other repositories
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
Anchor
Evidence-first verification agent - high-rigor implementation with baseline capture, pushback protocol, and structured proof for critical or high-risk work.