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 nahisaho/katashiro --skill musubix-sdd-workflowgit clone --depth 1 https://github.com/nahisaho/katashiroWrote 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/nahisaho/katashiro/musubix-sdd-workflow)<a href="https://agentmods.dev/skills/nahisaho/katashiro/musubix-sdd-workflow"><img src="https://agentmods.dev/badge/skills/nahisaho/katashiro/musubix-sdd-workflow/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/nahisaho/katashiro/musubix-sdd-workflow"><img src="https://agentmods.dev/badge/skills/nahisaho/katashiro/musubix-sdd-workflow.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.00051 | $0.01268 |
| Opus 5 | $0.00026 | $0.00634 |
| Sonnet 5 | $0.00010 | $0.00254 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
musubix-sdd-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MUSUBIX SDD Workflow Skill
This skill guides you through the complete SDD workflow for MUSUBIX projects.
Prerequisites
Before starting any development task:
- Read
steering/directory for project context - Check
steering/rules/constitution.mdfor the 9 constitutional articles - Review existing specs in
storage/specs/
Complete Workflow
Phase 1: Requirements Definition
Step 1: Create Requirements Document (Article IV - EARS Format)
Create requirements using EARS patterns:
# REQ-[CATEGORY]-[NUMBER]
**種別**: [UBIQUITOUS|EVENT-DRIVEN|STATE-DRIVEN|UNWANTED|OPTIONAL]
**優先度**: [P0|P1|P2]
**要件**:
[EARS形式の要件文]
**トレーサビリティ**: DES-XXX, TEST-XXX
EARS Patterns:
- Ubiquitous:
THE [system] SHALL [requirement] - Event-driven:
WHEN [event], THE [system] SHALL [response] - State-driven:
WHILE [state], THE [system] SHALL [response] - Unwanted:
THE [system] SHALL NOT [behavior] - Optional:
IF [condition], THEN THE [system] SHALL [response]
Step 2-3: Requirements Review Loop
Review requirements for:
- EARS format compliance
- Completeness and clarity
- Testability
- Traceability readiness
Repeat until no issues remain.
Phase 2: Design
Step 4: Create Design Document (Article VII - Design Patterns)
Create C4 model design documents:
- Context Level: System boundaries and external actors
- Container Level: Technology choices and container composition
- Component Level: Internal structure of containers
- Code Level: Implementation details
Design document template:
# DES-[CATEGORY]-[NUMBER]
## トレーサビリティ
- 要件: REQ-XXX
## C4モデル
### Level 2: Container
[PlantUML diagram]
## コンポーネント設計
[Component details]
Step 5-6: Design Review Loop
Review design for:
- Requirement coverage
- SOLID principles compliance
- Design pattern appropriateness
- Traceability to requirements
Repeat until no issues remain.
Phase 3: Task Decomposition
Step 7: Generate Tasks
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 · 211 lines · 51 tokens per session scan A d22e496942eb
musubix-sdd-workflow is a skill published in the GitHub repository nahisaho/katashiro (0 stars, last pushed 7mo ago), licensed MIT. It adds 51 tokens to every session and 1,268 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…