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-report-writinggit 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-report-writing)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/8d-report-writing"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/8d-report-writing/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/rbraga01/quality-engineering-skills/8d-report-writing"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/8d-report-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.02772 |
| Opus 5 | $0.00046 | $0.01386 |
| Sonnet 5 | $0.00018 | $0.00554 |
| Haiku 4.5 | $0.00009 | $0.00277 |
Grade A, and why
8d-report-writing 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
8D Customer Report Writing
When to use
Use when an 8D investigation is complete and a formal report must be submitted to the customer. This skill covers the writing quality and format — the methodology is in 8d-problem-solving.
The 8D report is a legal and commercial document. It is used by the customer to:
- Verify their claim was addressed
- Confirm containment protected their production
- Audit your corrective action quality
- Assess your supplier quality level for BIQS scoring, PPAP status, and future business decisions
A poorly written report — even with good corrective actions — signals low quality maturity.
OEM format references
| OEM | Format | Submission system |
|---|---|---|
| Ford | 8D (Ford 8D form) | Covisint / GSDB / portal |
| BMW | G8D (Global 8D) | SupplierPortal (SIM) |
| VW / Audi | QMSS (Lieferantenselbstauskunft) | SupplyOn |
| Stellantis (ex-FCA, PSA) | 8D | CQMS |
| Mercedes-Benz | 8D / ATC | SupplyOn |
| Toyota (TMMNA) | 8D or A3 | SMART |
Always download the current customer template from the portal before writing. Templates change. Always align with the specific customer format and mandatory fields — do not modify OEM templates.
Required 8D Report Checklist
☐ Correct OEM template used (latest version — downloaded before writing) ☐ D2 fully quantified and matches the customer claim and NCR exactly ☐ D3 containment implemented with evidence — past tense only ☐ D3 containment active until D6 verification is complete ☐ D4 includes both occurrence and escape root causes, each validated with objective evidence ☐ D5 actions directly address each root cause (RCO and RCE referenced) ☐ D6 includes objective verification data with justified sample size ☐ D7 includes PFMEA, CP, WI updates with revision numbers, plus horizontal deployment ☐ D8 includes champion sign-off and customer notification of closure ☐ All dates are chronological and consistent across D0–D8 ☐ All statements are supported by attached or referenced evidence ☐ No speculative, apologetic, or subjective language used ☐ Consistent tense: past for completed actions, present for current state
What ships with it
1 file 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.
- 11d ago First seen · 269 lines · 92 tokens per session scan A b6691229397b
8d-report-writing is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (28 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 2,772 once invoked, about $0.0005 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
aqe-ruflo
Add optional Ruflo development-time orchestration to an Agentic QE workflow. Use when a task benefits from coordinated swarms, persistent cross-session memory, routing, or Ruflo hooks. Do not use for a one-shot edit, and never add Ruflo to shipped AQE runtime dependencies.
aqe-plan-work
Build dependency-aware execution plans for complex Agentic QE, Ruflo, integration, migration, or multi-stream engineering programs. Use when Codex must turn research or requirements into phased work, select a small AQE fleet, map critical paths and parallel streams, define acceptance gates, or sequence risky changes.…
aqe-research
Conduct evidence-first technical research for Agentic QE, Ruflo, related ruvnet projects, or external tools. Use when Codex must investigate a repository, compare current upstream changes, trace dependencies and history, distinguish verified facts from inference, or synthesize findings into actionable engineering…
aqe-plan-quality
Create risk-based quality and test plans for Agentic QE changes. Use when scoping a feature, translating requirements into verification work, selecting QE specialties, assessing testability, or deciding which .claude/agents/v3/qe-.md capabilities should inform a task. Do not use merely to execute an already-defined…
aqe-test-change
Design, implement, and run durable tests for Agentic QE code changes. Use when adding tests, reproducing a defect, filling a coverage gap, selecting affected Vitest suites, checking CLI/MCP parity, or verifying a fix in this repository. Do not use for a read-only quality review with no requested edits.
aqe-review-quality
Review Agentic QE changes and issue an evidence-backed quality verdict. Use for code review, regression-risk assessment, release readiness, quality-gate evaluation, security/performance/testability review, or checking whether a change has sufficient verification. Do not use when the user primarily asks to implement a…