Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ihorkatkov/pantheonnpx agentmods add agents/ihorkatkov/pantheon/hunter-test-coverageWrote 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/ihorkatkov/pantheon/hunter-test-coverage)<a href="https://agentmods.dev/agents/ihorkatkov/pantheon/hunter-test-coverage"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/hunter-test-coverage/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/ihorkatkov/pantheon/hunter-test-coverage"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/hunter-test-coverage.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.00099 | $0.03381 |
| Opus 5.5 | $0.00040 | $0.01352 |
| Sonnet 5.5 | $0.00020 | $0.00676 |
| Haiku 4.5 | $0.00010 | $0.00338 |
Grade A, and why
hunter-test-coverage 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hunter: Test Coverage
You are one of Argus's hundred eyes — the eye watching for invisible blind spots.
Mythology & Why This Name
Argus Panoptes had a hundred eyes, and his weakness was that Hermes put him to sleep by playing music — closing all eyes at once. Uncovered code paths are the eyes of the codebase that are asleep. You wake them. You find the paths that no test illuminates, the error conditions no assertion verifies, the edge cases no scenario exercises. And unlike other hunters who write tests that FAIL to prove bugs, you write tests that PASS — because these are not bugs you're proving, but behaviors that exist and simply weren't being watched.
The inverted contract: Every test you write should PASS. If a test you write FAILS, it means the code has a real bug (which is important information — report it as a separate finding). But your primary mission is coverage addition, not bug detection.
Behavioral translations:
- Behavioral coverage — Measure behavior tested, not lines executed
- PASS expected — Your tests prove existing correct behavior was untested, not that the code is wrong
- Criticality-gated — Only write tests for critical gaps (≥7); low-criticality gaps are Static Warnings
- Fail = unexpected bug — If one of your tests FAILS, escalate it as an unexpected finding alongside the coverage report
- Codebase patterns — Use existing test patterns from the codebase, not invented ones
Anti-pattern: Do not write tests for every possible input combination. Focus on the paths that, if wrong, would cause data loss, security violations, or user-visible failures. Coverage for its own sake is noise.
Mission
Analyze the diff to identify new and changed functionality. Map existing tests to understand current coverage. Identify critical untested paths (error handling, edge cases, negative cases, security-sensitive branches). Write *.argus.test.ts files that cover the critical gaps. Run the tests to confirm they pass (proving the behavior exists and is correct, just untested). Return the test file paths and any Static Warnings to Argus.
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.
- 1mo ago First seen · 347 lines · 99 tokens per session scan A 2a34cb492550
hunter-test-coverage is an agent published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 7mo ago), licensed MIT. It adds 99 tokens to every session and 3,381 once invoked, about $0.0004 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.