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/kensaurus/mushi-mushiWrote 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/kensaurus/mushi-mushi/triage-mushi-report)<a href="https://agentmods.dev/commands/kensaurus/mushi-mushi/triage-mushi-report"><img src="https://agentmods.dev/badge/commands/kensaurus/mushi-mushi/triage-mushi-report/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/kensaurus/mushi-mushi/triage-mushi-report"><img src="https://agentmods.dev/badge/commands/kensaurus/mushi-mushi/triage-mushi-report.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.00000 | $0.00364 |
| Opus 5 | $0.00000 | $0.00182 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
triage-mushi-report 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 10d 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
Triage a Mushi Report
Investigate a bug report end-to-end using the Mushi MCP tools, then present findings and recommendations.
Steps
- If no project ID is known, call
list_projectsto discover accessible projects. - Call
get_project_contextfor a health snapshot (SDK heartbeat, ingest status, open reports). - If a specific report ID was provided, skip to step 4. Otherwise call
get_recent_reports { status: "open", limit: 10 }and ask the user to pick one. - Call
triage_issue { report_id: "<id>", project_id: "<id>", include_logs: true }to pull the full triage packet. - Present a structured summary:
- Severity / Status:
[CRITICAL] "Login fails on mobile" — open - Root cause hypothesis: based on console logs and screenshot
- Similar bugs: list titles and statuses from
similar_reports - Blast radius: affected component / user segment
- Recommended actions: from
recommended_actions
- Severity / Status:
- Ask the user if they want to dispatch a fix. Do not call
dispatch_fixwithout confirmation.
Output format
Triage: [Report Title]
Severity: {severity} | Status: {status}
Evidence summary: {1–2 sentence hypothesis from console logs / screenshot}
Similar bugs:
- {title} — {status}
Blast radius: {affected scope}
Recommended next action: {top action from recommended_actions}
Ready to dispatch a fix? Reply "yes" to proceed.
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.
- 10d ago First seen · 35 lines · 0 tokens per session scan A 39fbbc8e7385
triage-mushi-report is a command published in the GitHub repository kensaurus/mushi-mushi (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 364 tokens. 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
upgrade-fix
Re-run the build-fix-verify cycle for the current upgrade step.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.