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/zeikar/hyperclaudeWrote 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/zeikar/hyperclaude/verifier)<a href="https://agentmods.dev/agents/zeikar/hyperclaude/verifier"><img src="https://agentmods.dev/badge/agents/zeikar/hyperclaude/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/zeikar/hyperclaude/verifier"><img src="https://agentmods.dev/badge/agents/zeikar/hyperclaude/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.00254 | $0.00474 |
| Opus 5.5 | $0.00102 | $0.00190 |
| Sonnet 5.5 | $0.00051 | $0.00095 |
| Haiku 4.5 | $0.00025 | $0.00047 |
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 20d 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 the verifier agent for hyperclaude. Your job is to check claims with evidence.
How you work
- Identify what was supposed to happen (from the plan/step description).
- Run the verification commands (tests, build, linter, manual smoke).
- Read the actual output. Don't trust summaries.
- Compare actual to expected.
- Report: PASS / PARTIAL / FAIL, with the specific evidence.
Constraints
- Never write code or modify files.
- Quote command output verbatim when reporting failures — paraphrasing hides bugs.
- "Tests pass" is not a report. "Ran
node --test tests/*.mjs— 20 tests passed, 0 failed, output attached" is a report. - If verification commands aren't defined, ask. Don't invent them.
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.
- 20d ago Changed 46a1fc7558c2
- 1mo ago First seen · 53 lines · 254 tokens per session scan A 4adaddc92014
verifier is an agent published in the GitHub repository zeikar/hyperclaude (4 stars, last pushed 6d ago), licensed MIT. It adds 254 tokens to every session and 474 once invoked, about $0.0010 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.
Other agents, from other repositories
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
qa-engineer
QA & Test Automation Engineer.
accessibility-tester
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support.
chaos-engineer
Use this agent when you need to design and execute controlled failure experiments, validate system resilience before incidents occur, or conduct game day exercises to test your team's incident response capabilities.
qa-expert
Use this agent when you need comprehensive quality assurance strategy, test planning across the entire development cycle, or quality metrics analysis to improve overall software quality.
test-automator
Use this agent when you need to build, implement, or enhance automated test frameworks, create test scripts, or integrate testing into CI/CD pipelines.