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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/context-status)<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/context-status"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/context-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gonzalezpazmonica/savia/context-status"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/savia/context-status.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00292 |
| Opus 5 | $0.00007 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
context-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- context-status — 100% identical, 0 lines differ
What it actually says
/context-status
Show current context window status and recommendations.
Steps
- Read SAVIA_* env vars (set by model-capability-resolver at session start)
- Count loaded rules, skills, and agents in current session
- Calculate estimated token usage
- Show optimization recommendation
Output format
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📊 Context Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Model ................ {SAVIA_DETECTED_MODEL}
Context window ....... {SAVIA_CONTEXT_WINDOW} tokens
Tier ................. {SAVIA_MODEL_TIER}
Compact threshold .... {SAVIA_COMPACT_THRESHOLD}%
Strategy ............. {lazy_loading level}
Recommendation ....... {action}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If --json argument, output as JSON instead.
Recommendations
- If tier=fast: "Consider /compact frequently — 200K window fills fast"
- If tier=high: "Normal operation — /compact at ~65%"
- If tier=max: "Full capacity — /compact only if performance degrades"
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.
- 2d ago First seen · 44 lines · 14 tokens per session scan A 27557a5097b6
context-status is a command published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 292 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-09-06.
Other commands, from other repositories
remember
Consolidate stashes + friction into project memory.
chain-load
Loads the most recent chain link to continue work from a previous session.
stash
Stash session context [name].
sm-search
Ad-hoc semantic search over the supamem dual-memory collection.
handoff
Emit a handoff artifact for this session (optionally specify a slug).
resume-from
Boot this session from a handoff artifact (slug, latest, or path).