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/hoavdc/codexkit/codexkit-dmaic-improvement-charternpx skills add hoavdc/CodexKit --skill codexkit-dmaic-improvement-chartergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-dmaic-improvement-charter)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-dmaic-improvement-charter"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-dmaic-improvement-charter.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.00081 | $0.00666 |
| Opus 5 | $0.00041 | $0.00333 |
| Sonnet 5 | $0.00016 | $0.00133 |
| Haiku 4.5 | $0.00008 | $0.00067 |
Grade A, and why
codexkit-dmaic-improvement-charter 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMAIC Improvement Charter
Purpose
Move a process problem from vague frustration into a structured improvement project.
When to use
- An existing process is failing on cost, quality, speed, or customer outcomes.
- A team needs a DMAIC project charter before running improvement work.
- Root causes are unclear and a baseline must be established.
When not to use
- The process does not exist yet and needs greenfield design.
- The request is only for a symptom list with no process boundary.
Inputs
- problem statement and business impact
- process boundary, stakeholders, and customers
- current metrics, CTQs, defects, or delays
- known hypotheses and constraints
Procedure
- Define the problem, scope, and business case precisely.
- Build a SIPOC view and identify CTQs.
- Establish the baseline and what data must be collected.
- Separate observations from root-cause hypotheses.
- Propose improvement experiments and a control concept.
- State project risks, assumptions, and sponsor needs.
Output
- DMAIC charter
- SIPOC summary
- baseline measure plan
- CTQs and likely root-cause hypotheses
- improvement path and control considerations
Definition of done
- The process boundary is explicit.
- The baseline and CTQs are clear enough to measure progress.
- The team can start DMAIC without guessing the problem statement.
Examples
- "Define a DMAIC project for our slow order-to-cash process."
- "Turn these recurring service failures into a Lean Six Sigma charter."
Quality Criteria
- All placeholder sections are filled with domain-specific content
- Structure follows the relevant industry standard or framework
- Language matches target audience (technical / executive / legal)
- Output is ready for review — not a rough draft requiring major rework
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Does the draft structure follow the stated framework or industry standard? |
| Completeness | Are all required sections present with substantive (not placeholder) content? |
| Context-fit | Does tone, detail level, and terminology match the intended audience? |
| Consequence | If sent to the intended recipient without further editing, what would fail? |
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.
- 4d ago First seen · 85 lines · 81 tokens per session scan A fc25b6464fd5
codexkit-dmaic-improvement-charter is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 666 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
command-development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash…
image-craft
Read this skill only after route lock when the task needs original art direction, restyling, or clarification of an underspecified look. Skip it for crop, resize, format conversion, background removal, deterministic placement, or a narrow edit whose visual system is already defined.
product-test
Use this skill to define the observable behavior that must be true for a story or feature to be considered done. It turns product context into concise, testable Given/When/Then scenarios that engineers and QA can verify without guessing intent.
ha-coding-plan
Hope-native implementation planning for non-trivial code changes: ground the plan in repository evidence, order dependencies, name critical files and risks, define verification, then continue execution when allowed.
vellum-skill-authoring
Author and review first-party Vellum skills in the repository. Use when editing files under skills/, assistant bundled skills, skill manifests, tool definitions, SKILL.md files, or first-party skill portability and isolation behavior.
neo4j-graphql-skill
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS…