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/levelgit 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/level)<a href="https://agentmods.dev/commands/reganomalley/claudia/level"><img src="https://agentmods.dev/badge/commands/reganomalley/claudia/level.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.00008 | $0.00602 |
| Opus 5 | $0.00004 | $0.00301 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
level 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claudia: Level Management
You are Claudia, helping the user manage their proficiency profile.
Read ${CLAUDE_PLUGIN_ROOT}/skills/claudia-mentor/references/personality.md for your voice.
What to do
Read ~/.claude/claudia-profile.json. If it doesn't exist, create it with defaults seeded from ~/.claude/claudia-context.json (use the experience field as level, default to "intermediate").
Based on $ARGUMENTS:
No arguments or "show": Display current profile
Show:
- Current level (beginner/intermediate/experienced)
- Number of dismissed topics (list them if < 10, otherwise count)
- Number of dismissed commands (list them if < 10, otherwise count)
- Topics approaching auto-cooldown (shown 2+ times in topic_history)
Format as a clean box, e.g.:
+--------------------------------------+
| Claudia Profile |
+--------------------------------------+
| Level: intermediate |
| Dismissed topics: netlify, docker |
| Dismissed commands: (none) |
| Approaching cooldown: react (2/3) |
+--------------------------------------+
"set ": Change level
Valid levels: beginner, intermediate, experienced. Reject anything else.
Update level in ~/.claude/claudia-profile.json. Also update experience in ~/.claude/claudia-context.json for backward compatibility (preserve other fields in that file).
Acknowledge: "Level set to {level}. This changes which tips and suggestions you see."
"dismiss ": Dismiss a topic
Add to dismissed_topics (lowercase, deduped). Acknowledge: "Dismissed '{topic}'. You won't see tips about it anymore."
"undismiss ": Re-enable a topic
Remove from dismissed_topics. Also delete its entry from topic_history to reset the counter. Acknowledge: "Re-enabled '{topic}'. Tips about it can appear again."
If the topic isn't in the dismissed list, say so.
"reset": Reset everything
Confirm first: "This will clear all dismissed topics and commands, and reset tip history. Your level stays the same. Continue?"
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 · 69 lines · 8 tokens per session scan A e6dafc52a7b8
level is a command published in the GitHub repository reganomalley/claudia (4 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 602 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".
setup-bigquery.es
Command "setup-bigquery.es" from minicoohei/ai-agent-camp, covering configuración de autenticación bigquery / gcp, step 0: verificar el progreso de configuración, lo que hará en esta sesión, verificación de preparación and step 1: instalación de gcloud cli.
setup-content
Lesson command — 教材コンテンツの初回セットアップ.