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/nwave-ai/nwave/nw-quality-frameworknpx skills add nWave-ai/nWave --skill nw-quality-frameworkgit clone --depth 1 https://github.com/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-quality-framework)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-quality-framework"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-quality-framework.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.00023 | $0.02942 |
| Opus 5 | $0.00012 | $0.01471 |
| Sonnet 5 | $0.00005 | $0.00588 |
| Haiku 4.5 | $0.00002 | $0.00294 |
Grade A, and why
nw-quality-framework 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 yesterday.
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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Framework
Commit Readiness Gates (11)
All pass before committing:
- Active acceptance test passes (not skipped, not ignored)
- All unit tests pass
- All integration tests pass
- All other enabled tests pass
- Code formatting validation passes
- Static analysis passes
- Build validation passes (all projects)
- No test skips in execution (ignores OK during progressive implementation)
- Test count within behavior budget
- No mocks inside hexagon
- Business language in tests verified
Note: Reviewer approval (formerly Gate 12) and Testing Theater detection (formerly Gate 13) enforced at deliver-level Phase 4 (Adversarial Review via /nw-review), not per step.
Quality Gates by Category
- Architecture: all layers touched | integration points validated | stack proven E2E | pipeline functional
- Implementation: real functionality (not placeholders) | automated pipeline | happy path coverage | production patterns
- Business Value: meaningful user value | testable AC | measurable success metrics
- Real Data: golden masters present | edge cases tested | no silent errors | API assumptions documented
- Test Integrity: every test falsifiable | behavioral assertions only | no circular verification | no mock-dominated tests | no assertion-free tests | no fixture theater (see below)
Testing Theater Pattern 8: Fixture Theater
Definition: Acceptance tests pass because test fixtures create the expected end-state directly, rather than exercising production code through the driving port. Tests verify the correct outcome from the WRONG source.
Detection: After GREEN phase, run git diff --name-only. If files_to_modify
from the roadmap step have NO changes but tests flipped from RED to GREEN, this is
Fixture Theater. The test fixtures are implementing the feature, not production code.
Litmus test: Delete the new production code (or revert production files to pre-GREEN state). If tests still pass, it's Fixture Theater.
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.
- yesterday First seen · 224 lines · 23 tokens per session scan A a2225528f8de
nw-quality-framework is a skill published in the GitHub repository nWave-ai/nWave (604 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 2,942 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
git-commit-helper
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
landing
End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.
commit
Create a focused commit from the current staged changes. Use when asked to commit, prepare a commit, or finalize a Symphony-for-Trello issue branch.
git-ops
Commit, push, safely rebase an existing branch, create/read/update/close a pull/merge request (GitHub PR or GitLab MR), cut a feature branch, create/resume a managed worktree, or release. Triggers — gcam / gcamp / gcampr / rebase / 解决冲突 / 提 PR / 提 MR / pull request / merge request / 看 PR / 看 MR / 关 PR / 关 MR /…
gcamp
Commit current changes and push, without creating a pull/merge request. Use when the user says "gcamp" or wants to commit + push (e.g. add a commit to an existing PR/MR branch).