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/blueprint)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/blueprint"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/blueprint/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/blueprint"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/blueprint.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.00015 | $0.00510 |
| Opus 5 | $0.00008 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
blueprint 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 12d 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.
What it actually says
/architect:blueprint
Trigger
/architect:blueprint [optional description or mode]
Supported modes (when existing blueprint detected):
/architect:blueprint deepen— skip prompt, go straight to deepen mode/architect:blueprint update— skip prompt, go straight to update mode/architect:blueprint regenerate— skip prompt, go straight to full regenerate/architect:blueprint [description]— fresh project or interactive prompt for existing blueprint
Workflow
Follow these steps in order. Do not skip steps. Do not generate deliverables before understanding requirements.
This command is split across five files for size (each part is a continuation of the previous — read them in order):
| Part | File | Steps |
|---|---|---|
| 1 | command-parts/blueprint-1.md |
Step 0 (headless context) · Step 0.5 (detect existing blueprint) · Step 1 (load intent) · Step 2 (gather requirements) · Step 2.5 (multi-tenancy detection) |
| 2 | command-parts/blueprint-2.md |
Step 3 (build system manifest) · Step 3.5 (generate SDL document) |
| 3 | command-parts/blueprint-3.md |
Step 4, deliverables 4a–4h (executive summary through DevOps blueprint) |
| 4 | command-parts/blueprint-4.md |
Step 4, deliverables 4i–4o (cost estimate through sprint backlog) |
| 5 | command-parts/blueprint-5.md |
Step 4, deliverables 4p–4s (SDL sections) · Step 4.5 (write _state.json) · Step 4.6 (log activity) · Step 4.7 (signal completion) · Step 5 (docs publish, optional) · Step 6 (CTA footer) |
Read command-parts/blueprint-1.md through command-parts/blueprint-5.md in order (paths relative to the plugin root). Do not skip a part — later parts assume context established in earlier ones (manifest from Part 2, SDL sections from Parts 3–5).
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.
- 12d ago First seen · 32 lines · 15 tokens per session scan A 1e330d99637d
blueprint is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 510 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-08-31.
Other commands, from other repositories
nyann:retrofit
Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.
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:hotfix
Create the branch topology for a patch release against a previously tagged version. Ensures release/ . exists from the source tag, then creates hotfix/ off it. After this, the user commits the fix and runs /nyann:release from the hotfix branch.
nyann:release
Cut a release: generate a CHANGELOG section from Conventional Commits, make a release commit, and create an annotated tag. Defaults to conventional-changelog strategy.
nyann:ship
Open a GitHub pull request AND merge it in one step. Default uses GitHub's native auto-merge (returns immediately with outcome:"queued"); --client-side polls for green CI in the foreground then runs gh pr merge. Requires gh installed + authed.
nyann:cleanup-branches
Prune local branches whose work is already merged into the base. Lists candidates first, then applies on --yes. Mirrors the safe-delete semantics of git branch -d (lowercase d): nothing unmerged is touched.