agent-brain: Command for Claude Code

.claude/commands/challenge.md

challenge is a command for Claude Code from Railly/agent-brain. It costs 16 tokens per session (1,293 once invoked), scanned B, original, MIT.

A command that examines your notes about a belief or decision and builds an evidence-based case against it. It is designed to challenge your assumptions instead of simply agreeing with them.

In plain words
What is it for?
Use it to test choices about careers, startups, programming languages, learning plans, or other long-term decisions.
Why use it?
It helps expose weak evidence, overlooked risks, and conflicting information in your own thinking.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

This is Railly/agent-brain's own configuration. It tells Claude Code how to work on agent-brain itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-brain configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Railly/agent-brain. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Railly/agent-brain/main/.claude/commands/challenge.md
Clone the repo
git clone --depth 1 https://github.com/Railly/agent-brain

Made for: Claude Code.

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 challenge

README.md
[![agentmods](https://agentmods.dev/badge/commands/railly/agent-brain/challenge/github.svg)](https://agentmods.dev/commands/railly/agent-brain/challenge)
Your own site
<a href="https://agentmods.dev/commands/railly/agent-brain/challenge"><img src="https://agentmods.dev/badge/commands/railly/agent-brain/challenge/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 challenge

Your own site · 80×15
<a href="https://agentmods.dev/commands/railly/agent-brain/challenge"><img src="https://agentmods.dev/badge/commands/railly/agent-brain/challenge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 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,293 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00016 $0.01293
Opus 5.5 $0.00006 $0.00517
Sonnet 5.5 $0.00003 $0.00259
Haiku 4.5 $0.00002 $0.00129

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

Security

Grade B, and why

challenge scanned grade B 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 2mo 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.

Strips warnings and disclaimersmediumAnti-refusal

Omitting safety caveats hides risk from the user and is a common jailbreak preamble.

- Don't lecture about "both sides", take a clear position in the verdict
.claude/commands/challenge.md · 171 lines

How it starts

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

Read your current thinking on a topic and argue against it. Anti-sycophancy engine.

Usage: /challenge {topic or belief}

Examples:

  • /challenge YC is the right path for my startup
  • /challenge I should focus on Rust
  • /challenge v0 templates are worth my time
  • /challenge I need to learn math for ML
  • /challenge this is the best long-term career move

WAVE 0: Understand the Belief (PARALLEL)

# Tool Call Purpose
1 Grep Search $ARGUMENTS keywords across 03_Garden/concepts/, 02_Journal/daily/, 04_Projects/ Direct mentions in vault
2 Grep Search $ARGUMENTS keywords in 05_Areas/ Area-specific context
3 Read CLAUDE.md Goals and priorities context
4 Grep Search $ARGUMENTS keywords in 02_Journal/weekly/ Weekly goal history

WAVE 1: Map the Belief

Synthesize what you currently believe about this topic:

YOUR POSITION (as I understand it)
Topic: "{topic}"

Current stance:
{What you've written/done that supports this belief}

Evidence from your vault:
1. [{date}] {daily/note}: "{relevant quote or action}"
2. [{date}] {daily/note}: "{relevant quote or action}"
3. [{date}] {daily/note}: "{relevant quote or action}"

Strength of conviction: {HIGH/MEDIUM/LOW}
(based on: frequency of mentions, actions taken, resources invested)

Present this first. "Is this an accurate read of your position?"

If you correct it, I'll adjust before proceeding.

WAVE 2: Build the Counter-Case

Construct the strongest possible argument AGAINST the belief. Use these lenses:

Lens 1: Opportunity Cost

What are you NOT doing because of this belief?

OPPORTUNITY COST
By pursuing {belief}, you're implicitly deprioritizing:
- {thing 1} (evidence: {n} days since last engagement)
- {thing 2} (was in goals but dropped)
Time invested: ~{hours/weeks} based on commit/note frequency
What if that time went to {alternative}?

Lens 2: Survivorship Bias

Are you cherry-picking evidence?

SURVIVORSHIP BIAS
You remember: {the wins, the positive signals}
You might be ignoring:
- {failed attempt from vault}
- {abandoned related project}
- {negative signal you noted but didn't act on}

Read the full file on GitHub · 171 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. 2mo ago First seen · 171 lines · 16 tokens per session scan B 7b291a928291

Subscribe to this mod's changes

challenge is a command published in the GitHub repository Railly/agent-brain (22 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,293 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

challenge compared with commands from other repositories

challenge next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
challengeRailly/agent-brainCommand223mo agoMITB16Claude Code
minutes-ideassilverstein/minutesCommand1.6kyesterdayMITA48Claude Code, OpenCode
learnReflexioAI/claude-smartCommand7913d agoApache-2.0A14Claude Code
memory-storeverygoodplugins/mcp-automemCommand66todayMITA10Claude Code
analyze-contextRohiRIK/OpenLtmCommand298d agoMITA39Claude Code
cc-memoryTheLobbi/claudeCommand217d agoMITA0Claude Code
lians-recallLians-ai/LiansCommand175d agoApache-2.0A19Claude Code