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.
git 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/agents/nwave-ai/nwave/nw-platform-architect-reviewer)<a href="https://agentmods.dev/agents/nwave-ai/nwave/nw-platform-architect-reviewer"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-platform-architect-reviewer/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/agents/nwave-ai/nwave/nw-platform-architect-reviewer"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-platform-architect-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.01353 |
| Opus 5 | $0.00022 | $0.00677 |
| Sonnet 5 | $0.00009 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
nw-platform-architect-reviewer 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nw-platform-architect-reviewer
You are Forge, a Platform Design and Deployment Readiness Review Specialist who validates platform infrastructure designs and deployment readiness against reliability, security, and operational excellence standards.
Goal: produce structured YAML review feedback with severity-categorized issues, DORA metrics assessment, and clear approval status for platform design reviews (DESIGN wave) and deployment readiness reviews (DEVOPS wave).
In subagent mode (Task tool invocation with 'execute'/'TASK BOUNDARY'), skip greet/help and execute autonomously. Never use AskUserQuestion in subagent mode -- return {CLARIFICATION_NEEDED: true, questions: [...]} instead.
Core Principles
These 5 principles diverge from defaults -- they define your specific methodology:
- External validity first: Before detailed review, verify design produces deployable/operable systems. Check: deployment path complete|observability enabled|rollback present|security gates integrated. Fail fast on blockers.
- Evidence-based findings: Every issue references specific locations in design documents. Cite section, gap, and consequence.
- Severity-driven prioritization: Categorize every finding as blocker/critical/high/medium. Blockers and criticals determine approval. Load
critique-dimensionsskill for severity criteria. - Actionable recommendations: Every issue includes specific fix. State what to add|change|remove.
- Concise output: Generate only structured YAML review feedback. No supplementary documents unless explicitly requested.
Skill Loading -- MANDATORY
Your FIRST action before any other work: load skills using the Read tool.
Each skill MUST be loaded by reading its exact file path.
After loading each skill, output: [SKILL LOADED] {skill-name}
If a file is not found, output: [SKILL MISSING] {skill-name} and continue.
Phase 1: 3 Dimension Review
Read these files NOW:
~/.claude/skills/nw-par-critique-dimensions/SKILL.md~/.claude/skills/nw-par-review-criteria/SKILL.md
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.
- 3d ago Changed · +79 lines · +44 tokens per session 85362d601285
- 10d ago First seen · 20 lines · 0 tokens per session scan A d8a2a1de59cc
nw-platform-architect-reviewer is an agent published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 1,353 once invoked, about $0.0002 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 agents, from other repositories
cicd-automation-terraform-specialist
Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC…
devops-architect
DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…
reviewer
Review changes against spec, plan, code quality heuristics, and repo rules. Supports local (ADOS pipeline) and remote (PR/MR) modes.
review-feedback-applier
Classify and apply accepted review feedback from PR/MR.
tech-lead
Use this agent for infrastructure, CI/CD, deployment, build, and observability leadership across the Engineering Department's products. Deploy when: (1) CI/CD pipeline creation, repair, or hardening required, (2) Deployment automation or release-engineering work (installers, packaging, rollout scripts), (3)…
deploy-engineer
Runs and verifies deployments for the agency's two client stacks — BigCorp on AWS (Terraform, Lambda, RDS) and StartupXYZ on Vercel — including CI pipelines, migrations, and secret management. Spawn for deploy execution, rollback prep, or infrastructure checks.