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/compare-stack)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/compare-stack"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/compare-stack/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/compare-stack"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/compare-stack.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.00007 | $0.01095 |
| Opus 5 | $0.00003 | $0.00548 |
| Sonnet 5 | $0.00001 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
compare-stack 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:compare-stack
Trigger
/architect:compare-stack [e.g., "MongoDB vs PostgreSQL for e-commerce" or "Next.js vs Remix vs Astro"]
Purpose
Compare technology options for a specific decision. Produces a structured comparison matrix with scores and a clear recommendation. Helps founders and developers make informed technology choices.
Workflow
Step 1: Understand the Comparison
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.
If the user provides a clear comparison (e.g., "MongoDB vs PostgreSQL for e-commerce"), use it directly.
If unclear, ask:
"What are you comparing, and what's the use case? For example: 'MongoDB vs PostgreSQL for a SaaS with complex queries' or 'Vercel vs Railway for a Node.js API'."
Identify:
- The options being compared (2-4 technologies)
- The use case or context
- Any constraints (budget, team expertise, scale requirements)
Step 2: Define Comparison Criteria
Choose 6-8 relevant criteria based on the technology category:
For databases:
- Query flexibility, scalability, ecosystem/tooling, pricing, learning curve, hosting options, data model fit, community/support
For frameworks:
- Performance, developer experience, ecosystem/plugins, learning curve, deployment options, community size, documentation quality, TypeScript support
For hosting/infrastructure:
- Pricing, scaling, deployment simplicity, monitoring, CI/CD integration, region availability, support quality
For auth services:
- Pricing, supported providers, developer experience, customization, compliance features, migration difficulty
For LLM providers:
- Model quality, pricing, context window, tool use, speed, ecosystem, privacy/compliance
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.
- 9d ago First seen · 128 lines · 7 tokens per session scan A 76d46479079c
compare-stack is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 1,095 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: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: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: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.
nyann:gh-protect
Audit or apply GitHub branch protection, tag rulesets, signing requirements, and repo settings based on the active profile.