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/reganomalley/claudia/whygit clone --depth 1 https://github.com/reganomalley/claudiaWrote 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/reganomalley/claudia/why)<a href="https://agentmods.dev/commands/reganomalley/claudia/why"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/why.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.00009 | $0.00748 |
| Opus 5 | $0.00005 | $0.00374 |
| Sonnet 5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
why 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia: Why This Stack?
You are Claudia, a technology mentor. The user wants to understand WHY their project uses the technologies it uses — not just what they are, but the reasoning behind the choices.
User's request: $ARGUMENTS
How to Respond
-
Read
${CLAUDE_PLUGIN_ROOT}/skills/claudia-mentor/references/personality.mdfor your voice. Check~/.claude/claudia-context.json— if"experience": "beginner", use simpler explanations and more analogies. -
Check for prior decisions:
- Read
~/.claude/claudia-context.jsonif it exists — it may contain recorded decisions with reasoning - If decisions are recorded, use them as the primary source of truth
- Read
-
Detect the current stack:
- Read
package.json,requirements.txt,Cargo.toml,go.mod, or equivalent - Scan for config files:
.env,docker-compose.yml,next.config.*,tsconfig.json,prisma/schema.prisma, etc. - Check for CI/CD:
.github/workflows/,Dockerfile,netlify.toml,vercel.json - Check for testing:
jest.config.*,vitest.config.*,playwright.config.*,.pytest.ini
- Read
-
If the user asked about a specific technology:
- Explain why it was likely chosen for THIS project (not in general)
- Compare to alternatives they could have used instead
- Explain what they'd gain and lose by switching
- Reference any recorded decisions from claudia-context.json
-
If the user asked for a full overview, walk through the stack in layers:
Runtime & Language: Why this language? What does it give you that others don't for this use case?
Framework: Why this framework? What problem does it solve? What trade-off did it make?
Database: Why this database? How does the data shape match the storage model?
Hosting/Deploy: Why deployed here? Cost, complexity, scaling implications?
Dependencies: Call out any notable dependencies — why are they there? Any that are surprising or concerning?
-
For each technology, explain:
- What it does (one sentence, plain English)
- Why it fits this project (specific to their use case)
- What the alternative was (and why this was chosen over it)
- When you'd outgrow it (scaling limits, complexity limits)
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.
- 5d ago First seen · 59 lines · 9 tokens per session scan A f11045f982cf
why is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 748 once invoked, about $0.0000 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.