Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add navraj007in/architecture-cowork-plugin/plugin install architectWrote 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/scaffold)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/scaffold"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/scaffold/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/scaffold"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/scaffold.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.00009 | $0.10725 |
| Opus 5 | $0.00005 | $0.05362 |
| Sonnet 5 | $0.00002 | $0.02145 |
| Haiku 4.5 | $0.00001 | $0.01073 |
Grade A, and why
scaffold 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 — 744 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:scaffold
Trigger
/architect:scaffold
Purpose
After generating a blueprint with /architect:blueprint, this command creates actual project directories (or GitHub repos) and bootstraps each component with framework-appropriate starter code. Turns architecture specs into real, runnable projects.
Workflow
Quick Navigation
| Phase | Steps |
|---|---|
| Setup | Step 0.5 · Step 1 · Step 2 |
| Configuration | Step 3 · Step 3.5 · Step 3.6 |
| Pre-Scaffold | Step 3.7 · Step 3.8 |
| Generation | Step 4 · Step 4.5 |
| Completion | Step 5 · Step 5.5 · Step 6 · Step 6.5 |
Step 0.5: Load Prior Activity Context
Before anything else, load two levels of activity context.
Project level — check if architecture-output/_activity.jsonl exists. If it does, read the last 3 entries. Use them to understand:
- Which components have already been scaffolded and their overall outcome
- Whether a previous scaffold run was partial or failed
- What phase of work the project is in (blueprint done, scaffold done, active coding)
Component level — for any component that will be augmented (EXISTS), also read <component-name>/_activity.jsonl if it exists. Extract the last 3 entries to understand:
- What was scaffolded previously and which files were created
- What code changes have been made since scaffold
- Which files are likely to need updating vs which are safe to leave alone
Use both levels silently to inform decisions — do not print logs to the user unless asked. For example: if a component's log shows it was already scaffolded completely last run, skip its scaffold unless the user asks to re-run it.
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 · 744 lines · 9 tokens per session scan A 185ef13a387e
scaffold is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 10,725 once invoked, about $0.0000 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: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.