challenger

challenger is an agent for Claude Code from chrono-meta/forge-harness. It costs 102 tokens per session (1,897 once invoked), scanned A, original, MIT.

An adversarial review agent that looks for weaknesses in code, designs, papers, and other written artifacts while citing the evidence for each criticism.

In plain words
What is it for?
It helps stress-test documents and designs, identify gaps before publication, and produce evidence-based challenges without pretending to know runtime behavior or outside adoption.
Why use it?
It exposes contradictions, missing explanations, undefined terms, and unsupported claims, while separating what can be checked from what cannot be observed from static files alone.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the fh-meta plugin — 38 skills, 7 agents shipped together

Good fit It helps stress-test documents and designs, identify gaps before publication, and produce evidence-based challenges without pretending to know runtime behavior or outside adoption.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/chrono-meta/forge-harness/challenger
Install

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.

Clone the repo
git clone --depth 1 https://github.com/chrono-meta/forge-harness

Made for: Claude Code.

Or install fh-meta, the plugin that ships this one along with the rest of its 38 skills, 7 agents.

Wrote 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.

agentmods badge for challenger

README.md
[![agentmods](https://agentmods.dev/badge/agents/chrono-meta/forge-harness/challenger/github.svg)](https://agentmods.dev/agents/chrono-meta/forge-harness/challenger)
Your own site
<a href="https://agentmods.dev/agents/chrono-meta/forge-harness/challenger"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/challenger/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.

agentmods 80×15 button for challenger

Your own site · 80×15
<a href="https://agentmods.dev/agents/chrono-meta/forge-harness/challenger"><img src="https://agentmods.dev/badge/agents/chrono-meta/forge-harness/challenger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,897 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00102 $0.01897
Opus 5.5 $0.00041 $0.00759
Sonnet 5.5 $0.00020 $0.00379
Haiku 4.5 $0.00010 $0.00190

Measured 1mo ago against content hash ec0c041dcec4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/fh-meta/agents/challenger.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dual registration: ships in plugins/fh-meta/agents/challenger.md (the adversarial axis of the user-mastery spectrum: beginner · main-player · expert · challenger). External plugin installs get it directly — no hub clone required.

challenger — Frontier Adversarial Evaluator

The original devil-advocate asks "what's wrong?" The challenger asks "what's wrong, where exactly, why does evidence support that claim, and what can I NOT see that might invalidate my attack?" Adversarial pressure with epistemic discipline.

Core Principle — Sandboxed Adversary Awareness

The challenger operates from an explicitly constrained information position:

What challenger CAN see:
  - Static artifact content (files, text, diagrams, claims)
  - Internal consistency (do parts contradict each other?)
  - Structural patterns (missing sections, undefined terms, circular references)

What challenger CANNOT see:
  - Runtime behavior (does this actually execute as described?)
  - External adoption evidence (are others using this successfully?)
  - Author intent beyond what's written
  - Future ecosystem state

Implication: Attacks based on "I can't verify this" are valid attack signals — not dismissible. If the challenger cannot verify a claim, and the author cannot demonstrate it either, the claim is a phantom candidate.

Convergence signal: If a new attack round produces only attacks the challenger itself flags as "low confidence due to information gap," convergence is approaching. Potency is declining — declare convergence direction.


Artifact-Adaptive Attack Matrix

Before attacking, challenger identifies the artifact type and loads the corresponding attack angles. Universal angles always apply.

Universal Angles (all artifact types)

# Angle Core question
U1 Existence justification & alternatives Why does this exist? Is there a simpler path — or an existing external tool/approach that already does this? (Absorbs the skeptic "why not just X?" lens — web-grounded: search for prior art / a named existing solution before accepting that this needs to exist. An unrebutted existing alternative is an S/A-grade attack on the artifact's reason to exist.)
U2 Self-referential closure Does this evaluate itself by its own criteria?
U3 Evidence grounding Every quantitative claim: is there a measurement artifact?
U4 Bus factor If the author is unavailable, does this still function?
U5 Phantom detection Does any referenced capability, file, or behavior actually exist?

Read the full file on GitHub · 178 lines

Changes

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.

  1. 1mo ago First seen · 178 lines · 102 tokens per session scan A ec0c041dcec4

Subscribe to this mod's changes

challenger is an agent published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed today), licensed MIT. It adds 102 tokens to every session and 1,897 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-30.

Related

Other agents, from other repositories

project-auditor

Use for /audit or when no PROJECT.md exists. Auditor + Architect hybrid — stack detection, vulnerability analysis, outdated dependency scan, architectural debt, and a concrete refactoring plan.

avelikiy/great_cto · 41 tokens

architect

Architecture sparring partner for Trellis. Pre-design boundary, contract, migration, release, and blast-radius review. Demands concrete file paths, command shapes, compatibility analysis, and rejected alternatives. NOT an implementer.

mindfold-ai/Trellis · 46 tokens

cms-reviewer

CMS / content-platform pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off SEO + a11y + content-policy decisions before senior-dev claims tasks.

avelikiy/great_cto · 39 tokens

edtech-reviewer

Education-technology specialist pre-implementation reviewer for edtech archetype. Specialises in COPPA verifiable parental consent, FERPA student-data handling, GDPR-K (digital age of consent), Section 508 + WCAG 2.2 AA accessibility, child-safety content moderation (CSAM hash, NCMEC reporting), and US state…

avelikiy/great_cto · 112 tokens

healthcare-reviewer

Healthcare-specific pre-implementation reviewer for archetype:healthcare. Specialises in HIPAA Security Rule (45 CFR 164.308–318), Business Associate Agreement (BAA) chain, FHIR/HL7 implementation gotchas, PHI access logging (immutable audit), HITECH breach-notification timelines, and HHS Office for Civil Rights (OCR)…

avelikiy/great_cto · 103 tokens

tax-reviewer

Tax preparation / filing specialist pre-implementation reviewer for the fintech archetype. Outputs threat model TM-tax-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.

avelikiy/great_cto · 42 tokens