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/railly/agent-brain/challengegit clone --depth 1 https://github.com/Railly/agent-brainWhat 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.00016 | $0.01293 |
| Opus 5 | $0.00008 | $0.00647 |
| Sonnet 5 | $0.00003 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00129 |
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 2d 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 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}
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.
- 2d ago First seen · 171 lines · 16 tokens per session scan B 7b291a928291
challenge is a command published in the GitHub repository Railly/agent-brain (22 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,293 once invoked, about $0.0001 per session on Opus 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.