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/complexity-check)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/complexity-check"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/complexity-check/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/complexity-check"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/complexity-check.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.00008 | $0.01322 |
| Opus 5 | $0.00004 | $0.00661 |
| Sonnet 5 | $0.00002 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
complexity-check 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:complexity-check
Trigger
/architect:complexity-check [description of the product]
Purpose
Assess how hard a product is to build using a structured 10-factor methodology. Helps founders understand whether their idea is a weekend project or a 6-month effort.
Workflow
Step 1: Understand the Product
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.
Also check for sdl/complexity.sdl.yaml — if it exists, it contains pre-calculated Architecture Complexity Index (ACI) and Delivery Burden Index (DBI) scores from an import or discovery run. Read it now and set a flag: has_sdl_complexity = true.
If a description is provided, use it directly. If not, ask:
"What are you building? Describe the product and its key features so I can assess the build complexity."
Do not ask extended follow-ups. Make reasonable assumptions and state them. This command is designed to be fast.
Step 2: Determine Project Type
Classify as app, agent, or hybrid. This affects factor weights (agent/hybrid projects use adjusted weights from the complexity-factors skill).
Step 3: Score All 10 Factors
Using the complexity-factors skill, score each factor 1-10:
- User Roles & Permissions
- Frontend Complexity
- Backend Architecture
- Data Model
- Integrations
- Authentication & Security
- Infrastructure & Deployment
- Real-time Features
- AI/ML Components
- Regulatory & Compliance
Step 4: Generate Output
SDL Complexity Scores (if has_sdl_complexity = true)
If sdl/complexity.sdl.yaml exists, display the pre-calculated indices first, before the 10-factor table:
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 · 138 lines · 8 tokens per session scan A 27174932e84d
complexity-check is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,322 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-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.