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 nWave-ai/nWave --skill nw-par-review-criteriagit 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-par-review-criteria)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-par-review-criteria"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-par-review-criteria/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/nwave-ai/nwave/nw-par-review-criteria"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-par-review-criteria.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.00015 | $0.01034 |
| Opus 5.5 | $0.00006 | $0.00414 |
| Sonnet 5.5 | $0.00003 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
nw-par-review-criteria 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOp Reviewer: Review Criteria
Apply criteria only to the authorized operational/design scope and actual
deployment promise. This skill defines review dimensions, not a mandatory phase
sequence or artifact set. Existing authority and explicit no-rollout applicability
are valid. Project thresholds need their own evidence; percentages/time targets
below are not universal gates. Use the role-owned platform assessment in
nw-typesafe-system-one; local verified reasons and distinct real observations
decide findings, and scalar scores never compensate blockers.
Load nw-cross-cutting-invariants and apply flow:findings-go-to-the-owner-directly when exchanging findings or questions between roles.
Critique Dimension 1: Handoff adequacy
Compare the supplied authority/evidence against the operational decisions actually consumed by this task. A missing load-bearing interface, environment or recovery fact is a concrete finding; no fixed DISCUSS/DESIGN/DISTILL/DELIVER artifact or approval set is mandatory. DESIGN self-check is not an independent approval. Severity follows the consequence of the specific gap, not a phase label.
Critique Dimension 2: Deployment Readiness Gaps
Pattern: Feature marked "ready" but missing production prerequisites.
Require only the selected rollout's prerequisites: relevant current tests, configuration, promised telemetry, recovery and operational responsibilities. A document-only/no-rollout plan may be complete while live readiness remains unobserved; never require production validation outside authorization.
Severity: critical. Complete missing prerequisite before marking deployment-ready.
Critique Dimension 3: Traceability Violations
Pattern: Cannot trace production code back to requirements.
Required: User stories map to acceptance tests | Acceptance tests map to production code | Code changes traceable to commits | All AC verified in production.
Severity: high. Establish traceability chain: user-story -> acceptance-tests -> code-commits.
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 Changed 4a79b308d12a
- 2mo ago First seen · 110 lines · 15 tokens per session scan A a3d162a7be92
nw-par-review-criteria is a skill published in the GitHub repository nWave-ai/nWave (631 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,034 once invoked, about $0.0001 per session on Opus 5.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
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.