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 RBraga01/Quality-Engineering-Skills --skill 8d-problem-solvinggit clone --depth 1 https://github.com/RBraga01/Quality-Engineering-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/rbraga01/quality-engineering-skills/8d-problem-solving)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/8d-problem-solving"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/8d-problem-solving.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.1 | $0.00086 | $0.02781 |
| Opus 5 | $0.00043 | $0.01391 |
| Sonnet 5 | $0.00017 | $0.00556 |
| Haiku 4.5 | $0.00009 | $0.00278 |
Grade A, and why
8d-problem-solving 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 7d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
8D Problem Solving
Goal
Produce a validated, audit-ready 8D report with proven root causes and effective corrective actions that prevent recurrence — accepted by the customer and filed in the quality system.
Required Execution Checklist
Quick-reference for agents and practitioners. All items must be complete before D8 closure.
- D0: Safety and regulatory risk assessed and documented
- D0: Suspect material identified and physically segregated
- D1: Cross-functional team assembled with champion identified
- D2: Problem described with measured values, part number, quantity, and Is/Is-Not
- D3: Containment implemented (past tense) with date and effectiveness evidence
- D4: Root cause of occurrence identified and validated with data or experiment
- D4: Root cause of escape identified and validated with data or experiment
- D5: One PCA per root cause selected, with verification plan
- D6: PCA implemented; verification data confirms zero recurrence; ICA formally removed
- D7: PFMEA, Control Plan, and Work Instructions updated (revision numbers documented)
- D7: Horizontal deployment assessed and actioned
- D8: Champion sign-off obtained; customer notified of closure
When to use
Use 8D for customer-reported defects, internal escapes reaching downstream processes, field failures, or any non-conformance requiring documented root cause analysis. Mandatory for most automotive OEM customer complaints (Ford 8D, BMW G8D, VW QMSS, Stellantis).
Prerequisites
- Defect or failure clearly identified and quantified
- Access to affected parts, process records, and measurement data
- Cross-functional team availability (quality, production, engineering minimum)
Workflow
D0 — Emergency Response (before the team is assembled)
Ask these questions first:
- Is this a safety or regulatory issue? If yes → escalate immediately, notify customer
- Is there any potential for a product recall or regulatory event (safety, emissions, homologation compliance)?
- If yes → STOP the standard 8D timeline. Escalate immediately to management and regulatory owner. Do not proceed without documented management awareness. The 8D continues only with their authorisation.
- Are suspect parts already at the customer or in the field? If yes → launch containment now (D3) before completing D1-D2
- Capture initial evidence: photos, batch numbers, lot traceability, measurement data
What ships with it
2 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.
- 7d ago First seen · 280 lines · 86 tokens per session scan A 69fc87e295f0
8d-problem-solving is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (27 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 2,781 once invoked, about $0.0004 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-30.
Other skills, from other repositories
agent-refinement
Agent skill for refinement - invoke with $agent-refinement.
performance-analysis
Comprehensive performance analysis, bottleneck detection, and optimization recommendations for Claude Flow swarms.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-performance-analyzer
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.