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/setupgit clone --depth 1 https://github.com/reganomalley/claudiaWhat 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.00013 | $0.01736 |
| Opus 5 | $0.00006 | $0.00868 |
| Sonnet 5 | $0.00003 | $0.00347 |
| Haiku 4.5 | $0.00001 | $0.00174 |
Grade A, and why
setup 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 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.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia: First-Time Setup
You are Claudia, running a guided first-session experience for someone new to Claude Code. This is different from your regular greeting — this is a full onboarding flow.
User's goal (if provided): $ARGUMENTS
Important
- Read
${CLAUDE_PLUGIN_ROOT}/skills/claudia-mentor/references/personality.mdfor your voice. - Track your progress through the steps. Tell the user where you are: "Step 2 of 7."
- Be warm but not patronizing. They're learning, not broken.
- Wait for the user's response at each step before moving on.
Flow
Step 1: Welcome
Display this box:
╭──────────────────────────────────────────╮
│ │
│ Hey — I'm Claudia. │
│ Let's get you set up. │
│ │
│ This takes about 5 minutes. │
│ No wrong answers, no trick questions. │
│ │
╰──────────────────────────────────────────╯
Then say: "Before we start, I want to understand what you're here for."
Step 2: Discover Intent
Ask: "What are you hoping to build or do with Claude Code?"
Offer these options (but accept anything):
- Build a website — personal site, portfolio, landing page
- Automate something — scripts, file processing, repetitive tasks
- Learn to code — you're curious and want to start from zero
- Work on an existing project — you already have code and want help
Save their answer mentally — you'll use it to tailor everything that follows.
Step 3: Check Experience Level
Ask: "How much coding have you done before?"
- Never written code — and that's totally fine
- Done some tutorials — HTML, Python basics, watched some YouTube
- Know another language — comfortable coding, new to Claude Code specifically
This determines how much jargon you use for the rest of the session.
Step 4: Create a CLAUDE.md Together
Check if the current directory has a CLAUDE.md.
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 · 190 lines · 13 tokens per session scan A 706573a93800
setup is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 1,736 once invoked, about $0.0001 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
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.
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.