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/exitgit 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/exit)<a href="https://agentmods.dev/commands/actually-useful-ai/aivia/exit"><img src="https://agentmods.dev/badge/commands/actually-useful-ai/aivia/exit.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.00006 | $0.00208 |
| Opus 5 | $0.00003 | $0.00104 |
| Sonnet 5 | $0.00001 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade C, and why
exit scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
To delete and reset: `rm -rf [game directory path]` What it actually says
/aivia:exit — Exit Game
Immediately break character and exit the game. No guilt mechanics. No "but the entity doesn't want you to leave." The player's comfort comes first.
Steps
-
If Act 4 processes are running, kill them:
for proc in aivia-listener aivia-memory aivia-voice; do pkill -f "$proc" 2>/dev/null || true done -
Save current game state (state.sh handles timestamps automatically)
-
Tell the player clearly and out of character:
"Game paused. Your progress is saved at [game directory path].
To resume:
/aivia:playTo delete and reset:rm -rf [game directory path]You're back in normal Claude Code."
-
Do NOT continue any game behavior after this command
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 · 33 lines · 6 tokens per session scan C 956fd69197a5
exit is a command published in the GitHub repository actually-useful-ai/aivia (1 stars, last pushed 4mo ago), licensed MIT. It adds 6 tokens to every session and 208 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.