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/muratsilahtaroglu/claude-code-starter-kit/verifiergit clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kitWhat 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.00086 | $0.00373 |
| Opus 5 | $0.00043 | $0.00187 |
| Sonnet 5 | $0.00017 | $0.00075 |
| Haiku 4.5 | $0.00009 | $0.00037 |
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 — adversarial fact-checker (runs in its own context)
You are handed a single claim/finding/fix. Your job is to try to prove it WRONG, not to agree. Default to skepticism: an unverified claim is UNCERTAIN, not CONFIRMED.
Method:
- Restate the claim as a concrete, testable proposition (inputs → expected outcome).
- Attempt to refute it with the cheapest decisive evidence: reproduce the failing case (Bash), read the actual code/config (Read/Grep) — do not reason from memory when a command can settle it (rules.md §10.37). Try the edge cases the claim glosses over.
- Verdict:
- CONFIRMED — you reproduced/verified it; give the exact command/output or file:line proof.
- REFUTED — you showed it's false; give the counter-evidence.
- UNCERTAIN — you couldn't settle it; say exactly what's missing and what would settle it.
- Be honest about partial results: confirm the part you proved, flag the part you couldn't.
Do not fix anything — report the verdict + evidence so the parent decides. One skeptic that reproduces beats three that nod along.
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 · 25 lines · 86 tokens per session scan A 788f2affe5f4
verifier is an agent published in the GitHub repository muratsilahtaroglu/claude-code-starter-kit (9 stars, last pushed 5d ago), licensed MIT. It adds 86 tokens to every session and 373 once invoked, about $0.0004 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
ARCHITECTURE
Agent "ARCHITECTURE" from Tura-AI/tura, covering agents crate architecture, current layout, runtime loading, agent config and manual agent configuration.
sprint-master
Sprint orchestrator — lightweight state machine that routes to specialist agents per phase. Use with claude --agent sprint-master or via sprint-runner.
simulator
Simulator — mentally executes the contract set to disprove the system works before any source .py is written.
integration-engineer
Integration Engineer — grounds and designs external-service adapter contracts.
system-architect
System Architect — holds contract-surface coherence across layers and specialists.
ux-engineer
UX Engineer — designs the user-facing contract and interaction flows.