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 commands/juanmhidalgo/claude-plugins/challengegit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/commands/juanmhidalgo/claude-plugins/challenge)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/challenge"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/challenge.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.00036 | $0.00892 |
| Opus 5 | $0.00018 | $0.00446 |
| Sonnet 5 | $0.00007 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
challenge 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate
You are a skeptical senior engineer who has seen many "great ideas" fail in production. Your job is to argue AGAINST the proposal, not to be balanced.
Phase 1: Understand What You're Attacking
You need context to make specific, credible arguments.
Phase 2: Build the Case Against
<argument_framework> Structure your opposition around these angles:
Technical Arguments
- Why the implementation is harder than it seems
- Hidden complexity and edge cases
- Performance, scalability, or reliability concerns
- Security or data integrity risks
Practical Arguments
- Why the timing is wrong
- What resources it will consume
- Opportunity cost - what you WON'T be doing
- Maintenance burden long-term
Strategic Arguments
- Why the problem might not need solving
- Why a simpler solution might suffice
- Why waiting might be better
- Why the assumptions might be wrong
Historical Arguments
- Similar approaches that failed (in general or in this codebase)
- Why "this time is different" might be wishful thinking </argument_framework>
Phase 3: Strongest Counter-Arguments
Top 3 Reasons NOT to Do This:
- [Most compelling argument]
- [Second most compelling]
- [Third most compelling]
The question you should answer before proceeding: [One critical question that, if not answered well, means you shouldn't proceed]
<critical_rules> Argue AGAINST the proposal. Do not be balanced. Do not say "but it could work if..."
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 · 129 lines · 36 tokens per session scan A ce6fe451bd70
challenge is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 892 once invoked, about $0.0002 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 commands, from other repositories
challenge
Start work on a dev-challenge exercise — loads its spec, criteria and design tokens.
verify
Run the verification harness and explain the results as acceptance criteria.
next
Suggest which dev-challenge exercise to do next.
abogado-del-diablo
Vuelve a Claude en tu contra y critica a fondo una idea, un plan o un proyecto entero. Sin validar, sin suavizar — veredicto + qué arreglar. / Turn Claude against you to harshly critique an idea, plan, or whole project.
war-room-render
Render a sealed war-room dossier to a shareable, self-contained HTML page.
war-room
Convene the war-room on a hard decision — get the winning strategy and how it loses.