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/mvp-scope)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/mvp-scope"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/mvp-scope/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/mvp-scope"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/mvp-scope.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.00014 | $0.03302 |
| Opus 5 | $0.00007 | $0.01651 |
| Sonnet 5 | $0.00003 | $0.00660 |
| Haiku 4.5 | $0.00001 | $0.00330 |
Grade A, and why
mvp-scope 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:mvp-scope
Trigger
/architect:mvp-scope
Purpose
Define a sharp MVP boundary that maximizes learning while minimizing build time. Produces a prioritized feature set with user stories, complexity estimates, and clear cut criteria — preventing scope creep and ensuring the team builds the right v1.
Workflow
Step 1: Gather Context
Read in this order:
architecture-output/_state.json— read first if it exists; useproject,personas,market_research,mvp_scopedirectly — these replace reading intent.json, user-personas.md, and deep-research.mdintent.json— only if_state.json.projectis absent; extract name, vision, core features, business/technical constraintsarchitecture-output/problem-validation.md— only if it exists; Grep for "Problem Statement" and "Core Assumptions" sections onlyarchitecture-output/user-journeys.md— only if it exists; Grep for journey names and "Success state" lines onlyarchitecture-output/deep-research.md— only if_state.json.market_researchis absent; if reading, use Grep for the "Feature Comparison Matrix" and "Opportunity Gaps" sections onlyarchitecture-output/user-personas.md— only if_state.json.personasis absent; if reading, use Grep for persona names and "Features they'd use most"
Step 2: Define the MVP Thesis
Write a clear MVP thesis statement:
MVP Goal: Enable [primary persona] to [core action] so they can [measurable outcome], validated by [success metric].
Then define:
- Core value proposition — the ONE thing the MVP must prove
- Time constraint — target launch timeline (derive from intent.json or estimate based on scope)
- Team constraint — assumed team size (derive from intent.json or assume solo/small team)
- What this MVP is NOT — explicit anti-goals (3-5 things people might expect but aren't included)
Step 3: Feature Inventory
List ALL possible features mentioned across intent.json, personas, and research. For each:
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 · 294 lines · 14 tokens per session scan A e07f56071516
mvp-scope is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 3,302 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.