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 agentmods add skills/morodomi/dev-crew/diagnosenpx skills add morodomi/dev-crew --skill diagnosegit clone --depth 1 https://github.com/morodomi/dev-crewWrote 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/morodomi/dev-crew/diagnose)<a href="https://agentmods.dev/skills/morodomi/dev-crew/diagnose"><img src="https://agentmods.dev/badge/skills/morodomi/dev-crew/diagnose.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00853 |
| Opus 5 | $0.00021 | $0.00426 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
diagnose 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 3d 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.
This is a copy
92% identical to tdd-diagnose — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
TDD Diagnose Phase
複雑なバグに対し、複数の仮説を並行調査し根本原因を特定する。
Progress Checklist
DIAGNOSE Progress:
- [ ] バグ情報収集（カテゴリ・重要度・症状）
- [ ] 仮説生成（3つ以上）
- [ ] 調査実行（モード自動選択）
- [ ] 結果統合・分岐判定
- [ ] Cycle doc更新 → 完了メッセージ表示
Workflow
Step 1: バグ情報収集
1a. AskUserQuestion で構造化入力:
- バグカテゴリ: regression / new behavior / intermittent / performance degradation
- 重要度: blocking development / blocking users / workaround exists
1b. 続けて自然言語で質問:
- 「エラーメッセージやログを貼り付けてください」
- 「関連するファイルパスがあれば教えてください」
詳細: reference.md
Step 2: 仮説生成
収集した情報から原因候補を 3つ以上 リスト:
| # | 仮説 | 調査方針 |
|---|---|---|
| H1 | [原因候補1] | [検証方法] |
| H2 | [原因候補2] | [検証方法] |
| H3 | [原因候補3] | [検証方法] |
仮説テンプレート: reference.md
Step 3: 調査実行
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS 環境変数でモードを選択:
| 環境変数 | モード | 手順 |
|---|---|---|
有効 (1) |
討論型 (Agent Teams) | steps-teams.md |
| 無効 / 未設定 | 並行型 (Subagent) | steps-subagent.md |
Step 4: 調査結果統合
各仮説の検証結果を集約し、分岐判定:
根本原因が特定された場合 (Identified)
→ Cycle doc に根本原因を記録、Step 5 へ
2-3候補に絞込まれた場合 (Narrowed)
→ AskUserQuestion で候補からユーザーが選択、Step 5 へ
不明・全仮説否定の場合 (Inconclusive)
調査結果が不明確です。
1. 仮説を追加して再調査（最大2回まで）
2. 手動調査へエスカレート（現時点の発見事項を記録）
再調査2回で未解決の場合、選択肢2へ強制遷移。
Step 5: Cycle doc 更新 → 完了
調査結果を Cycle doc に記録。
================================================================================
DIAGNOSE完了
================================================================================
根本原因を特定し、Cycle docに記録しました。
次のステップ:
- Orchestrate使用時: 自動的にsync-planが実行されます
- 手動実行時: /spec でTDDコンテキスト設定を開始してください
================================================================================
Reference
- 詳細: reference.md
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 95 lines · 42 tokens per session scan A ac2aadf76824
diagnose is a skill published in the GitHub repository morodomi/dev-crew (1 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 853 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to tdd-diagnose, differing in 21 lines, and is treated as a copy.
Other skills, from other repositories
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
plan-orchestrate
Execute implementation plans with parallel TDD workers. Use when ready to run, execute, or start a plan. Triggers on "run the plan", "execute the plan", "implement the plan", "start the plan", "start implementation", "orchestrate", "begin autonomous execution". Requires a plan created by plan-create.
specify-incremental
Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over factory automation.
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…
project-setup
One-time interactive setup to configure a project for autonomous development. Use when setting up a new project for TDD-based autonomous development with HCF.