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 kensaurus/cursor-kenji --skill mushi-healthgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/mushi-health)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/mushi-health"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/mushi-health/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/kensaurus/cursor-kenji/mushi-health"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/mushi-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01652 |
| Opus 5 | $0.00036 | $0.00826 |
| Sonnet 5 | $0.00014 | $0.00330 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
mushi-health 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 8d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mushi Health Check
Degree of freedom: MIXED. First-red diagnosis [HIGH freedom];
Steps 1–6 in order [LOW freedom — run exactly].
How to reason
- Observe —
doctor,deploy check, keys, logs, cron — in that order - Interpret — first red is root vs downstream symptom
- Classify — creds / functions-down / keys / logs / cron-missing
- Severity — paused project or invalid API key outranks a quiet QA cron on a new project
Worked example
Observe:
mushi doctorgreen;mushi deploy check✗qa-story-runner;qa_story_runsempty for 2h. Interpret: first red is the runner; empty cron is downstream. Classify: function-down — checkget_logsforqa-story-runner; do not add keys yet. Verify: stop at Step 2; fix the runner; continue remaining steps only after it is green.
Self-critique before reporting
- In order — did not skip ahead of the first ❌
- Evidence — each row cites command output or a query, not memory
- Stopped to fix — first red was remediated before later steps
- Right owner — e2e loop proof →
mushi-integration; targeted diagnosis →diagnose_setup
Run these checks in order. Stop and fix at the first ❌ before continuing.
Component map
| # | Component | How to check |
|---|---|---|
| 1 | CLI credentials | mushi doctor |
| 2 | API + edge functions | mushi deploy check |
| 3 | Project overview | mushi status |
| 4 | BYOK key pool | mushi keys list or MCP list_byok_keys |
| 5 | Supabase logs | Supabase MCP get_logs |
| 6 | QA cron running | DB query on qa_story_runs |
Step 1 — CLI credentials [LOW freedom — run exactly]
mushi doctor
Expected output — all lines green:
✓ ~/.mushirc found
✓ MUSHI_API_KEY valid (mushi_...)
✓ MUSHI_API_ENDPOINT reachable (200 OK)
✓ MUSHI_PROJECT_ID matches a live project
✓ Feature flags fetched
Fix if red: Re-run mushi login --api-key mushi_... --endpoint https://<ref>.supabase.co/functions/v1/api --project-id <pid>.
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.
- 8d ago First seen · 202 lines · 72 tokens per session scan A d1dfb7d8354f
mushi-health is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 1,652 once invoked, about $0.0004 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering bugs, test failures, unexpected behavior, or any technical issue before proposing fixes.
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
incident-triage-harness
Production-style incident triage workflow for logs, metrics, code, safe mitigations, and M3 multimodal visual evidence (screenshots, screen recordings). Use when debugging alerts, regressions, outages, or suspicious runtime behavior.
agent-self-verification
A code-change verification workflow that builds the project, checks the interface and logs, and repeats fixes when something fails.
fix-issue
Fix a GitHub issue end-to-end. Use when given an issue number to fix, implementing bug fixes, or addressing reported problems.
debug-issue
Systematically debug a reported issue.