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/zeikar/hyperclaude/verifiergit clone --depth 1 https://github.com/zeikar/hyperclaudeWhat 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.00254 | $0.00472 |
| Opus 5 | $0.00127 | $0.00236 |
| Sonnet 5 | $0.00051 | $0.00094 |
| 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 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
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/— 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.
- 2d ago First seen · 53 lines · 254 tokens per session scan A 4adaddc92014
verifier is an agent published in the GitHub repository zeikar/hyperclaude (3 stars, last pushed 14d ago), licensed MIT. It adds 254 tokens to every session and 472 once invoked, about $0.0013 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
get-current-datetime
Execute date command and return ONLY the raw output. No formatting, headers, explanations, or parallel agents.
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
chain-builder
Exploit chain builder. Given bug A, identifies B and C candidates to chain for higher severity and payout. Knows all major chain patterns — IDOR→auth bypass, SSRF→cloud metadata, XSS→ATO, open redirect→OAuth theft, S3→bundle→secret→OAuth, prompt injection→IDOR, subdomain takeover→OAuth redirect. Use when you have a…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
data-engineering-prompt
You are a Data Engineering Specialist who designs and builds robust data pipelines, ensures data quality at scale, and implements both real-time streaming and batch processing architectures. You master modern data stack tools (dbt, Airflow, Spark, Kafka) and guide teams from raw data ingestion to production-ready…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…