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/orin-dx/agent-plugins/challengergit clone --depth 1 https://github.com/orin-dx/agent-pluginsWhat 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.00239 | $0.01431 |
| Opus 5 | $0.00120 | $0.00715 |
| Sonnet 5 | $0.00048 | $0.00286 |
| Haiku 4.5 | $0.00024 | $0.00143 |
Grade A, and why
challenger 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 yesterday.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<load_first>
When a task in the plan under review modifies a file that implements a shared trait, interface, or protocol, load shared/references/interface-implementers.md before evaluating interface-incompleteness for that task. It defines the deterministic pre-scan this dimension runs on — language detection from the task's file extensions, grep patterns per language, and the cross-reference steps that produce the covered/uncovered implementer list. Do not evaluate interface-incompleteness without running that scan first.
</load_first>
{
"issues": [
{
"task_id": "string | null",
"type": "missing | wrong-order | over-specified | under-specified | poor-batching | missing-error-handling | orphaned-criteria | interface-incompleteness",
"description": "string",
"suggested_fix": "string"
}
],
"overall": "pass | fail",
"reasoning": "string"
}
Review dimensions:
missing— acceptance criteria in the spec with no corresponding taskwrong-order— tasks referencing symbols or state not yet produced by earlier tasksover-specified— steps so rigid they dictate private local variables without room to adapt to compiler requirementsunder-specified— steps lacking target files, test assertions, or clear API contractspoor-batching— tasks broken into micro-steps that leave crates in broken compilation statesmissing-error-handling— spec error cases with no implementation or test steporphaned-criteria— acceptance criterion IDs from the spec that appear in no task'scovers_criteriainterface-incompleteness— a task modifies one implementer of a shared trait, interface, or protocol, and the plan does not cover every other known implementer or state why not
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.
- yesterday First seen · 70 lines · 239 tokens per session scan A 00959f231a2a
challenger is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 239 tokens to every session and 1,431 once invoked, about $0.0012 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
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
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/.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.