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/navraj007in/architecture-cowork-pluginWrote 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/commands/navraj007in/architecture-cowork-plugin/well-architected)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/well-architected"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/well-architected/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/commands/navraj007in/architecture-cowork-plugin/well-architected"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/well-architected.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.00013 | $0.01562 |
| Opus 5 | $0.00006 | $0.00781 |
| Sonnet 5 | $0.00003 | $0.00312 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade A, and why
well-architected 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 8d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:well-architected
Trigger
/architect:well-architected — full six-pillar review (default).
/architect:well-architected [pillar:X] — review one pillar only.
/architect:well-architected [pillars:X,Y] — review a named subset.
You can also pass an architecture description directly: /architect:well-architected [description of the architecture]
Pillars
| Pillar | What it evaluates |
|---|---|
opex |
Operational Excellence — deployability, runbooks, observability, incident response |
security |
Security — auth, encryption, least privilege, secrets management, dependency scanning |
reliability |
Reliability — redundancy, failover, backup/restore, chaos engineering, SLOs |
performance |
Performance Efficiency — caching, CDN, DB indexing, async patterns, load testing |
cost |
Cost Optimization — right-sizing, reserved capacity, data transfer, idle resources |
devex |
Developer Experience — CI/CD, local dev setup, documentation, onboarding time |
Examples:
/architect:well-architected [pillar:security]
/architect:well-architected [pillars:reliability,performance]
/architect:well-architected [pillar:cost] [non_interactive:true]
When a [pillar:...] or [pillars:...] tag is present, score and produce recommendations only for the named pillars. Still produce the summary scorecard but mark unreviewed pillars as "skipped". When absent, review all six pillars.
Purpose
Evaluate an architecture against 6 quality pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Developer Experience. Produces per-pillar scores, gap analysis, and a prioritized improvement roadmap.
Works as a standalone review of any architecture, or as a follow-up to /architect:blueprint.
Workflow
Step 1: Understand the Architecture
First, check architecture-output/_state.json. If it exists, read it in full — it provides instant access to project, tech_stack, components, design, entities, and personas without reading larger files. Use its values directly where available; fall back to SDL (check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files) only for detail not in _state.json.
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.
- 8d ago First seen · 154 lines · 13 tokens per session scan A 5a2d6a5f0552
well-architected is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,562 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 commands, from other repositories
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
nyann:wait-for-pr-checks
Poll a GitHub PR's checks until they all pass, any one fails, or a timeout is hit. Returns a structured outcome the caller can gate on.
nyann:watch
Start (or stop) a CI sentinel for the current repo's open PRs — a one-shot foreground poll by default, or a supervised background daemon with --daemon. Also manage a multi-repo watch-list and poll every watched repo at once. Notifications surface in your next session via the session-start hook.
nyann:gen-ci
Generate a GitHub Actions CI workflow (.github/workflows/ci.yml) from the project's nyann profile and detected stack. Produces lint, typecheck, and test jobs matching the hook configuration.
spec-release
Generate release notes, changelog, and deployment checklist.
aws-research
Research AWS services and architecture patterns using AWS Knowledge MCP for authoritative guidance.