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/cost-estimate)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/cost-estimate"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/cost-estimate/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/cost-estimate"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/cost-estimate.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.01725 |
| Opus 5 | $0.00005 | $0.00863 |
| Sonnet 5 | $0.00002 | $0.00345 |
| Haiku 4.5 | $0.00001 | $0.00172 |
Grade A, and why
cost-estimate 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 12d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:cost-estimate
Trigger
/architect:cost-estimate [description of the product or paste existing architecture]
Purpose
Produce a detailed cost estimate for any product idea or existing architecture. This is a standalone command — it doesn't require a prior blueprint.
Workflow
Step 1: Read Context & Understand What to Estimate
First, check for architecture-output/_state.json. If it exists, read it in full and extract:
project.nameandproject.description→ product context without asking the usertech_stack→ integrations, database, auth provider, deployment targets — use these directly to determine what services to include in the estimate; skip asking if the stack is already knowncomponents→ list of components with types — use to identify compute resources needed
If _state.json provides sufficient context (project description + tech stack), proceed directly to Step 2 without asking the user.
If no _state.json and the user provides a description, identify:
- What infrastructure is needed (compute, databases, storage)
- What third-party services are required
- Whether AI/LLM costs apply
If the user pastes an existing architecture or manifest, use that directly.
If context is still unclear after checking _state.json, ask one question:
"What are you building, and roughly how many users do you expect in the first 6 months?"
Step 1.5: Pull Live AWS Pricing (Optional)
After reading context, silently attempt a lightweight AWS MCP call (e.g. list_ec2_instances with maxResults: 1) to check if the server is connected.
If connected AND the tech stack includes AWS services, call the relevant tools to pull live resource data:
describe_ec2_instance_typesfor the instance family in the stack (e.g.t3,t4g) — use actual current pricing from the response rather thanpricing-tables.mdfor EC2describe_rds_instancesto check if the user has existing RDS instances — if so, note actual instance class and storage in the estimatelist_lambda_functions— if serverless is in the stack, check existing functions to understand memory/timeout config
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.
- 12d ago First seen · 196 lines · 10 tokens per session scan A 3ded8730f780
cost-estimate 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 1,725 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.