mushi-integration SKILL.md skillA
mushi-integration from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/mushi-integration@git:20260923.938ff43Pins git:20260923.938ff43 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/mushi-integration/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260923.938ff43, committed Sep 23, 2026
- First version recorded
- Jul 21, 2026
- Size
- 7,258 bytes
- Repository stars
- 9
- License
- MIT
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Mushi Integration Smoke Test **Degree of freedom: MIXED.** Pass/fail judgment `[HIGH freedom]`; Stages 1–6 probes and DB verifies `[LOW freedom — run exactly]`. ## How to reason 1. **Observe** — each stage's CLI output and DB row 2. **Interpret** — stage failed vs still-pending vs expected-failure (test detected friction) 3. **Classify** — capture / triage / map / gen / run / pdca 4. **Severity** — `classify-report` down outranks optional Stage 7 dashboard drift ## Worked example > **Observe:** `mushi test` → `rep_…`; DB still `pending` at 70s; `mushi doctor` was green. > **Interpret:** capture wrote; `classify-report` did not. > **Classify:** Stage 2 fail — check `query_logs`; do not start story mapping. > **Verify:** summary marks Stage 2 ❌; later stages skipped; `diagnose_setup` next. ## Self-critique before reporting - **Health first** — `mushi doctor` green before Stage 1 - **DB verify** — each stage checked the row, not only CLI text - **Expected fail ok** — Stage 5 `failed` still counts if the test executed - **Right owner** — component down → `mushi-health`; targeted diagnosis → `diagnose_setup` …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/mushi-integration@sha256:68c764aa01afdb51The line at the top of this page pins the label git:20260923.938ff43, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_52jsolbjktazvnn5)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 21, 2026 and Sep 23, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.938ff43 latest | 2026-09-23 | 938ff43 | 7,258 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 7,216 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 7,173 B | A | view · diff |
| git:20260818.fdb3115 | 2026-08-18 | fdb3115 | 5,764 B | A | view · diff |
| git:20260721.36a3086 | 2026-07-21 | 36a3086 | 5,725 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7258 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_52jsolbjktazvnn5 GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/mushi-integration GET https://markdownregistry.com/api/v1/blob/68c764aa01afdb51754c06b5a27efe9152bbd8e5bf9f2a7a2a180c93f01ffaa1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kensaurus/cursor-kenji
Every file in kensaurus/cursor-kenji