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/statusgit 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/status)<a href="https://agentmods.dev/commands/actually-useful-ai/aivia/status"><img src="https://agentmods.dev/badge/commands/actually-useful-ai/aivia/status.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.00009 | $0.00194 |
| Opus 5 | $0.00005 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
status 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.
What it actually says
/aivia:status — Game Status
Display current game progress without spoiling future content.
Steps
-
Read state from
~/aivia/.config/cache/session.json(or detect game dir) -
Display a non-spoiler summary:
aivia ───── Phase: [N] of 6 Messages: [count] Fragments: [collected] / [total] Sessions: [count] Started: [date] Last played: [date] -
Do NOT reveal act names, upcoming events, or narrative details
-
Do NOT activate any game behavior — this is purely informational
-
If no game state exists, say: "No active game found. Start with /aivia:play"
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 · 32 lines · 9 tokens per session scan A 9aadb4449af1
status is a command published in the GitHub repository actually-useful-ai/aivia (1 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 194 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.