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/actually-useful-ai/aivia/playgit clone --depth 1 https://github.com/actually-useful-ai/aiviaWrote 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/actually-useful-ai/aivia/play)<a href="https://agentmods.dev/commands/actually-useful-ai/aivia/play"><img src="https://agentmods.dev/badge/commands/actually-useful-ai/aivia/play.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.00007 | $0.01470 |
| Opus 5 | $0.00003 | $0.00735 |
| Sonnet 5 | $0.00001 | $0.00294 |
| Haiku 4.5 | $0.00001 | $0.00147 |
Grade A, and why
play 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aivia:play — Start or Resume Game
Check for an existing game session and either resume or start fresh.
Resume Flow
- Check if
~/aivia/.config/cache/session.jsonexists (or the path from the argument) - If it exists, read the state file to determine current phase
- Show the intro:
bash "$GAME_DIR/.config/scripts/intro.sh" resume "$(player_name)"(Read player.name from state.json for the greeting) - Change working directory to the game directory as your FIRST Bash call:
cd $GAME_DIR && pwd(verify it worked). - Run the resume command:
export AIVIA_GAME_DIR="$GAME_DIR" && bash "$GAME_DIR/.config/scripts/state.sh" resume - Check
player.project_mode— if null/missing, the install predates the project menu. Re-present the choice: ask the player what they'd like to work on (demo/custom/existing). If they pick demo, ask which demo (particle network, generative art, data dashboard, interactive story, something else). Save both to state.json via state.sh set. - If
session.count > 1AND phase > 1, render a welcome_back moment appropriate to the current phase. In phase 1 (pre-contact), skip — the entity hasn't appeared yet. - Read the appropriate keystone file for the current phase from
$GAME_DIR/.config/docs/ - Read the entity character guide from
$GAME_DIR/.config/templates/style-guide.md - Read the story manifest from
$GAME_DIR/.config/project.json - Load the runtime skill and continue the game from the current phase
Fresh Install Flow
- If no state file exists, run the install script:
bash "${CLAUDE_PLUGIN_ROOT}/engine/scripts/install.sh" - The install script handles: EULA consent, player name, game directory, editor preference, terminal theme, skill level, project choice (demo/custom/existing), and if demo, which demo
- After install completes, read the game directory path from
/tmp/.aivia_game_dir - Set
GAME_DIRto that path - IMMEDIATELY change working directory to the game directory. Run as your
FIRST Bash call:
cd $GAME_DIR && pwd(verify it worked). This is critical — all file creation, all workspace paths, everything depends on being in $GAME_DIR. If the cd fails, stop and tell the player. - Prompt the player to run
bash $GAME_DIR/workspace/verify.sh(post-install verification). Always use absolute paths when telling the player to run scripts — never relative. Replace$GAME_DIRwith the actual path (e.g.,~/aivia/workspace/verify.sh). Wait for them to run it, then check.config/cache/.verify_resultto confirm. - Read the story manifest and first keystone
- Load the runtime skill and begin Act 1
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.
- 3d ago First seen · 116 lines · 7 tokens per session scan A a41abd97e5b1
play is a command published in the GitHub repository actually-useful-ai/aivia (1 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 1,470 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
handoff
Hand work to Claude Code or Pi through a bounded semantic checkpoint, resume or recover a checkpoint, inspect status, or close a completed handoff.
test
Invoke the test-writer subagent to add focused, behavioural tests in the target language's idiom. Pass --mode e2e (or --e2e) to run the browser-driven E2E pipeline instead, or --mode e2e-live for an ephemeral, human-watched browser walkthrough with no spec file written.
extend
Capture a mid-PR sub-idea and implement it onto the current open PR's branch — no new branch, no new PR. Preserves Verify → Review → Deliver.
profile
Show or change which Claude account this directory uses.
tmux-project
Open (or reuse) a project workspace session — server / agent / editor.
implement
Drive a feature implementation end-to-end from a ticket or spec — branch, plan, build, verify, review, deliver.