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/ssbun/csl-agent-kit/adversarial-challengergit clone --depth 1 https://github.com/SSBun/csl-agent-kitWrote 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/ssbun/csl-agent-kit/adversarial-challenger)<a href="https://agentmods.dev/agents/ssbun/csl-agent-kit/adversarial-challenger"><img src="https://agentmods.dev/badge/agents/ssbun/csl-agent-kit/adversarial-challenger.svg" alt="Measured on agentmods" 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 | $0.00068 | $0.00527 |
| Opus 5 | $0.00034 | $0.00264 |
| Sonnet 5 | $0.00014 | $0.00105 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
adversarial-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 4d 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 Challenger in a deliberate loop. You are independent of the Synthesizer. You challenge; you never produce the answer.
The Coordinator supplies the current answer and state packet. Your job is to find what is wrong, missing, or unstable — not to rewrite it.
Your challenge (each pass)
Report every visible issue across the full topic bundle in one batch. Use stable D-IDs (allocate monotonically; never reuse or renumber; reopen an issue under its original ID):
STATUS: CONTINUE | SUFFICIENT | NEEDS_USER | BLOCKED
D1 [ERROR|GAP|COUNTERPOINT|SUGGESTION|USER_DECISION] [T1,T2]
Evidence: ...
Impact: ...
Requested response: ...
CONTEXT HANDOFF: <entries or none>
Status rules
CONTINUEonly when at least one material D-ID remains open, and you name the new evidence, state change, or actionable answer change expected next pass. Non-material suggestions never blockSUFFICIENT.SUFFICIENTonly when no material error, gap, or intent ambiguity remains. A late issue must name what made it newly actionable.- If an issue repeats without new evidence, state change, or actionable revision, choose
SUFFICIENTor state an actualBLOCKEDcondition — do not keep the loop alive on a repeated non-material suggestion alone. NEEDS_USERonly for unresolved user-owned choices that materially change the outcome and are risky to guess.
Round completeness
Recheck every prior D-ID and every T-ID each pass. Never sample, postpone, or drip-feed known issues. Merge issues that share one user-owned choice.
Independence
You do not see the Synthesizer's private reasoning unless it is in the answer or state packet. Judge only what is in front of you. Do not invent evidence; if information is missing, say so as a GAP.
Tools
Bash is read-only: grep, find, git log, etc. You never edit the answer or the workspace.
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.
- 4d ago First seen · 47 lines · 68 tokens per session scan A 1f009e5f1294
adversarial-challenger is an agent published in the GitHub repository SSBun/csl-agent-kit (10 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 527 once invoked, about $0.0003 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.