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 dmaicgit 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/dmaic)<a href="https://agentmods.dev/skills/rbraga01/quality-engineering-skills/dmaic"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/dmaic/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/dmaic"><img src="https://agentmods.dev/badge/skills/rbraga01/quality-engineering-skills/dmaic.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.00101 | $0.02703 |
| Opus 5 | $0.00051 | $0.01352 |
| Sonnet 5 | $0.00020 | $0.00541 |
| Haiku 4.5 | $0.00010 | $0.00270 |
Grade A, and why
dmaic 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMAIC (Six Sigma Problem Solving)
When to use
Use DMAIC when:
- A problem has recurred multiple times despite previous corrective actions
- The process needs measurable, data-driven capability improvement (Cpk improvement target)
- The root cause is unknown and requires statistical analysis to identify
- A customer requires a Six Sigma approach or asks for a DMAIC report
- The improvement opportunity involves eliminating chronic waste (rework, scrap, test failures)
Use 8D instead when: The problem is a single customer complaint, an escape to the field, or requires immediate containment. 8D is reactive and fast. DMAIC is proactive and thorough — it takes weeks to months.
Use PDCA instead when: The improvement is incremental and the root cause is already known or assumed.
Prerequisites
- A defined problem with measurable impact (reject rate, Cpk, scrap cost, defect count)
- Baseline data available or collectable
- Process owner and cross-functional team assigned
- Management support and a time budget (minimum 4–12 weeks depending on project scope)
Workflow
Phase 1 — DEFINE
Objective: Define the problem, the scope, the team, and the goal in measurable terms.
Key tools and deliverables:
Project Charter — The DMAIC starts and ends here. Contains:
- Problem statement: what is happening, where, since when, how much (measured impact)
- Goal statement: specific, measurable target (e.g., "Reduce connector reject rate from 3.2% to 0.5% by Q3")
- Scope: what is IN and OUT of scope (use Is/Is-Not to define boundaries)
- Business case: financial or customer impact ($, PPM, warranty cost)
- Team: Champion, Black Belt/Green Belt, process owner, operators, engineering
SIPOC diagram:
- Suppliers → Inputs → Process → Outputs → Customers
- Defines the process at a high level before diving into detail
- Identifies all inputs that could affect the output (Y)
Voice of the Customer (VOC) → CTQ:
- What does the customer care about? (VOC)
- Translate to a measurable Critical to Quality (CTQ) characteristic
- The CTQ becomes the Y (output) the project will improve
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.
- 10d ago First seen · 282 lines · 101 tokens per session scan A f6425c4f7108
dmaic is a skill published in the GitHub repository RBraga01/Quality-Engineering-Skills (28 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 2,703 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-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…
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.