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 skills add myths-labs/muse --skill context-health-checkgit clone --depth 1 https://github.com/myths-labs/museWrote 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/skills/myths-labs/muse/context-health-check)<a href="https://agentmods.dev/skills/myths-labs/muse/context-health-check"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/context-health-check/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/skills/myths-labs/muse/context-health-check"><img src="https://agentmods.dev/badge/skills/myths-labs/muse/context-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 102 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00025 | $0.00323 |
| Opus 5 | $0.00013 | $0.00161 |
| Sonnet 5 | $0.00005 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
context-health-check 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 4d 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
Context health
Use metrics exposed by the current client for the exact current session. Record observation time and limitations. Model specifications, user preferences, cached or cumulative token totals do not establish current context occupancy. A recent request input is an observation, not a prediction of remaining space.
If reliable metrics are unavailable, report UNKNOWN. Do not estimate occupancy from turn counts, source-file sizes, model names, or an old static model table.
At observed 80% pressure, save meaningful current-role/Lane deltas, reduce the next read batch, compact if the client supports it, verify the current checkpoint and continue the same work. A percentage alone never triggers full Bye, a new Lane, or a new conversation. After compaction, obtain a fresh observation; prior counts are stale. Compaction does not prove that all memory survived.
Preserve decisions, user corrections, constraints, unfinished failures, relevant evidence and the next action. The agent fills the save fields; the user need not write a template. Save at least every ten interaction rounds if changes remain unsaved. Only a legacy session without a Lane uses CRASH_CONTEXT.md; never replace another Lane's state.
Stop for an actual inability to continue, failed recovery, unresolved critical state contradictions, or an explicit user handoff request. Save confirmed facts and state what is missing. Do not represent partial recovery as a complete Bye.
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.
- 4d ago Changed · -164 lines · -23 tokens per session c4f5d5ab08ca
- 12d ago First seen · 195 lines · 48 tokens per session scan A b389c124f4e6
context-health-check is a skill published in the GitHub repository myths-labs/muse (32 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 323 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-30.
Other skills, from other repositories
help-flow
Help about Rosetta: explains capabilities and usage.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
external-lib-flow
Workflow for onboarding an external private library so AI can use it without source access.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
adhoc-flow
Workflow for the rest of tasks: lightweight documentation, build, track, synchronize, etc.
coding-agents-prompting-flow
Workflow for authoring and adapting AI-agent prompts: skills, agents, workflows, rules, etc.