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 fzfclee/consulting-skills --skill fishbone-diagramgit clone --depth 1 https://github.com/fzfclee/consulting-skillsWrote 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/fzfclee/consulting-skills/fishbone-diagram)<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/fishbone-diagram"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/fishbone-diagram/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/fzfclee/consulting-skills/fishbone-diagram"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/fishbone-diagram.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.00053 | $0.00753 |
| Opus 5 | $0.00026 | $0.00377 |
| Sonnet 5 | $0.00011 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
fishbone-diagram 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fishbone Diagram
Use this skill to run Fishbone Diagram as a practical consulting method, not as a generic framework explanation.
Method Notes
- Use categories such as people, process, systems, policy, environment, and measurement.
- Prioritize cause branches for evidence testing.
Required Inputs
Collect or infer these inputs before execution:
- problem statement
- observed symptoms
- process context
- candidate cause categories
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use for a single verified linear cause or treat category branches as proven causes. Fishbone analysis is for exploring multiple cause families that still require evidence.
Adjacent Methods
five-whys-root-cause: follow one selected branch deeper.systems-thinking: use for feedback and behavior over time.constraint-analysis: use for a proven binding bottleneck.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
|---|---|---|---|
| Define effect | Problem statement, defect, service failure, or outcome gap. | Place the problem at the head of the fishbone. | Effect statement. |
| Choose categories | Domain context. | Select people, process, systems, policy, environment, measurement, or custom categories. | Cause categories. |
| Populate causes | Evidence, team input, process facts. | List possible causes under each category. | Fishbone cause map. |
| Mark evidence | Cause map and available data. | Label causes as evidenced, assumed, contradicted, or unknown. | Evidence-coded fishbone. |
| Prioritize tests | Evidence-coded fishbone. | Choose top cause branches and validation tests. | Root-cause test plan. |
Output Template
### 1. Effect And Boundary
Observed effect:
Location / period:
Baseline:
In scope / out of scope:
### 2. Cause Map
| Category | Possible cause | Evidence status | Mechanism |
|---|---|---|---|
| | | | |
### 3. Priority Causes
| Cause | Impact if true | Testability | Confidence |
|---|---|---|---|
| | | | |
### 4. Test Plan
| Test | Owner | Timing | Confirming / disconfirming signal |
|---|---|---|---|
| | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:
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.
- 11d ago First seen · 87 lines · 53 tokens per session scan A f006b492121f
fishbone-diagram is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 22d ago), licensed Apache-2.0. It adds 53 tokens to every session and 753 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
thinking-scientific-method
When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
thinking-map-territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
thinking-kepner-tregoe
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
fable-operator
Use when a substantive request needs verified, calibrated reasoning — analysis, diagnosis, review, advice, or a draft the user will act on — even when rigor is not asked for, and most of all when being wrong is expensive or irreversible. NOT casual chat (rigor theater), NOT the SDD gates verify, debug, review; this is…
s4h-logic-causality-mapping
Map causal relationships, trace dependencies, and reason about consequences before acting. Use when you need to understand what causes what, what breaks if something changes, or what must be true for a plan to work. TRIGGERS: 'map the dependencies', 'what causes this', 'what breaks if I change X', 'trace the root…