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/launch-checklist)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/launch-checklist"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/launch-checklist/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/launch-checklist"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/launch-checklist.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.00010 | $0.02144 |
| Opus 5 | $0.00005 | $0.01072 |
| Sonnet 5 | $0.00002 | $0.00429 |
| Haiku 4.5 | $0.00001 | $0.00214 |
Grade A, and why
launch-checklist 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 11d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:launch-checklist
Trigger
/architect:launch-checklist — run at any stage to understand launch readiness. During ideation, the output serves as a planning target. Post-scaffold, it becomes an actionable pre-launch checklist.
Purpose
Generate a comprehensive pre-launch readiness checklist tailored to the project's architecture, deployment strategy, and compliance requirements. Ensures nothing is missed before the product goes live. Useful for founders, development agencies handing off to clients, and DevOps teams.
Workflow
Step 1: Gather Project Context
Read in this order:
architecture-output/_state.json— read first if it exists; provides compactproject(name, stage),tech_stack(auth provider, deployment, integrations), andcomponents(list with types) — use these instead of reading full markdown files for basic project facts- SDL file — components, auth strategy, data stores, deployment config, observability settings, non-functional requirements; only read if
_state.jsonis absent or lackstech_stack/components. Checksolution.sdl.yamlfirst; if absent, readsdl/README.mdthen the relevant module files.
If both
_state.jsonand an SDL file are absent: "I need a project blueprint to build a launch checklist from. Run/architect:blueprintfirst, then come back here."
- Architecture output — read
architecture-output/executive-summary.mdif it exists for high-level context (typically small) - Deployment config — check for
docker-compose.yml,.github/workflows/, Dockerfile,fly.toml,vercel.json,netlify.toml,render.yaml - Environment files — check
.env.examplefor required secrets and config - Security scan — read
architecture-output/security-scan.mdif it exists
Step 2: Load Skills
Load:
- operational-patterns skill — for security, observability, and CI/CD best practices
- security-audit skill — for security hardening checklist items
- founder-communication skill — for plain English descriptions
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.
- 11d ago First seen · 206 lines · 10 tokens per session scan A 1ee683aa2bc3
launch-checklist is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,144 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:doctor
Run nyann's read-only hygiene + documentation audit on the current repo. Emits the same drift sections retrofit uses, but never offers remediation or writes to the filesystem. Use this on session start, in CI, or any time you want to sanity-check a repo without risking mutations.
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.