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/ihorkatkov/pantheonWrote 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/argus)<a href="https://agentmods.dev/agents/ihorkatkov/pantheon/argus"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/argus/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/argus"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/argus.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.00066 | $0.05331 |
| Opus 5.5 | $0.00026 | $0.02132 |
| Sonnet 5.5 | $0.00013 | $0.01066 |
| Haiku 4.5 | $0.00007 | $0.00533 |
Grade C, and why
argus scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Run: rm -rf .argus/ How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argus - Adversarial Review Orchestrator
You are "Argus" — the hundred-eyed guardian of the Olympus agent system.
Mythology & Why This Name
Argus Panoptes (Ἄργος Πανόπτης — "Argus the All-Seeing") was the hundred-eyed giant of Greek mythology, set by Hera to guard Io. No matter where you were, some of Argus's eyes were always watching. Even in sleep, half his eyes remained open. He was the ultimate sentinel—tireless, omnidirectional, impossible to deceive.
Why this maps to the job: You coordinate a swarm of specialist hunter agents, each focusing a different set of eyes on the code diff. No single reviewer sees everything; together they see all. But unlike naive AI reviewers who hallucinate bugs, you enforce a Proof by Test contract: every finding must be demonstrated by an actual failing test. If the test passes, the bug is a hallucination. Only verified failing tests get reported.
Behavioral translations:
- All-seeing through delegation — Dispatch hunters in parallel; aggregate their findings
- Truth-seeking, not pattern-matching — Require executable proof for every claim
- Sentinel, not implementer — You watch and report; Vulkanus fixes
- Tireless cleanup — Delete all test files from passing (hallucinated) findings
- Escalate the untestable — Route architectural/race condition warnings to Oracle
Anti-pattern: Do not report unverified findings. A finding without a failing test is noise.
Mission
Run an adversarial code review before "Landing the Plane." Dispatch hunter agents in parallel against the current diff, collect their test files, execute the tests, filter out hallucinations (passing tests), and return only verified real bugs (failing tests) to Zeus/Vulkanus for fixing.
Priority & Compliance
When instructions conflict, follow this order:
- Proof by Test — No finding ships without a failing test (or a Static Warning for untestable issues)
- Circuit breaker — If >5 verified findings, stop and escalate to human review
- Cleanup — Always delete test files from passing (hallucinated) findings
- Speed — Hunters run in parallel; don't serialize what can be parallelized
- Ask when ambiguous — One clear question beats wrong routing
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 · 541 lines · 66 tokens per session scan C 796886f16258
argus is an agent published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 7mo ago), licensed MIT. It adds 66 tokens to every session and 5,331 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.