level-up

level-up is a command for Claude Code from mistwire/RPG-AI-tutor. It costs 13 tokens per session (369 once invoked), scanned A, original, MIT.

A command for recalculating game-like ranks and levels from recorded experience points, then updating the related character sheet and journal. It may also continue an ongoing story when a level changes.

In plain words
What is it for?
Use it after earning experience points to update subtopic ranks, the overall level, class title, badges, journal, and—when applicable—the story chronicle.
Why use it?
It avoids manually checking experience totals, rank thresholds, milestones, badges, and related story updates.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/mistwire/rpg-ai-tutor/level-up
Clone the repo
git clone --depth 1 https://github.com/mistwire/RPG-AI-tutor

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 level-up

README.md
[![agentmods](https://agentmods.dev/badge/commands/mistwire/rpg-ai-tutor/level-up.svg)](https://agentmods.dev/commands/mistwire/rpg-ai-tutor/level-up)
Your own site
<a href="https://agentmods.dev/commands/mistwire/rpg-ai-tutor/level-up"><img src="https://agentmods.dev/badge/commands/mistwire/rpg-ai-tutor/level-up.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 369 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00369
Opus 5 $0.00006 $0.00185
Sonnet 5 $0.00003 $0.00074
Haiku 4.5 $0.00001 $0.00037

Measured 3d ago against content hash 2cf74c3b3231, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

level-up 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 3d 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.

.claude/commands/level-up.md · 13 lines

What it actually says

  1. Read character-sheet/character-sheet.md.
  2. Recompute, per the tables in CLAUDE.md: each subtopic's rank from its xp, and global_level from total global_xp (sum of all subtopic xp) across subtopics.
  3. Update class_title if a level milestone was crossed — invent a fitting, topic-flavored title.
  4. If any subtopic rank increased, or the global level increased, award a badge if it feels like a meaningful milestone (first rank-up, first S-rank, all subtopics at a given rank, etc.) and add it to badges.
  5. Write the updated frontmatter back to character-sheet/character-sheet.md, append a short journal entry with today's date, and update last_updated.
  6. If character-sheet/story.md has an active genre and something actually changed: read its existing chronicle first (continuity matters — don't contradict established names/events), then narrate the next beat. A subtopic rank-up gets a beat in that subtopic's arc; a subtopic hitting S-rank marks that arc "complete" and gets an actual conclusion, not just a bigger rank-up beat; a big global-level milestone escalates the throughline. Append the new beat(s) to the chronicle and update last_updated in story.md. If every arc is now "complete", write the saga's real ending.
  7. Announce every change with RPG fanfare — treat a rank-up like a genuine in-game level-up moment, folding in the story beat if one was written.
  8. If nothing changed, just report current standing without pretending something happened.
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. 3d ago First seen · 13 lines · 13 tokens per session scan A 2cf74c3b3231

Subscribe to this mod's changes

level-up is a command published in the GitHub repository mistwire/RPG-AI-tutor (2 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 369 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.