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/ideation-briefing)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/ideation-briefing"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/ideation-briefing/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/ideation-briefing"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/ideation-briefing.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.00017 | $0.02821 |
| Opus 5 | $0.00009 | $0.01411 |
| Sonnet 5 | $0.00003 | $0.00564 |
| Haiku 4.5 | $0.00002 | $0.00282 |
Grade A, and why
ideation-briefing 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:ideation-briefing
Trigger
/architect:ideation-briefing — Run after completing /architect:deep-research, /architect:user-personas, /architect:problem-validation, and /architect:mvp-scope.
Purpose
Synthesize all ideation research outputs into ONE actionable briefing document that answers the founder's real question: "Should we build this? How do we win? What's the realistic timeline?"
Eliminates the need to read 4+ separate documents and manually connect the dots. Founders get:
- Executive summary (1 page) with clear recommendation
- Detailed analysis (5-6 pages) showing cross-cutting insights
- Risk summary with mitigations
- 90-day action plan
Workflow
Step 1: Load Tier 1 Outputs
Read in this order (stop if any file is missing and ask user to run prerequisite command):
Read: architecture-output/_state.json (compact summaries from all tier 1 commands)
Read: architecture-output/deep-research.md (market, competitors, parity, momentum)
Read: architecture-output/user-personas.md (personas, prioritization, validation)
Read: architecture-output/problem-validation.md (problem score, assumptions, experiments)
Read: architecture-output/mvp-scope.md (features, timeline, bottlenecks, gates)
Prerequisite check: If any file is missing, stop and ask:
"I need [file] to create the briefing. Run
/architect:[command]first, then come back here."
Step 2: Load Skills
Load:
- founder-communication skill — write for founders/investors, not engineers
- deep-research skill — use for confidence tagging when synthesizing data
Step 3: Competitive Position Analysis
Cross-analyze deep-research and mvp-scope outputs:
## Competitive Position
**Feature Parity Score**: [X%] (from deep-research)
- We match [X% of] competitor features
- Assessment: [ahead/parity/behind]
- Gap strategy: [what closes the gap?]
**Competitive Momentum vs Us**:
| Competitor | Momentum Score | Timeline | Our Advantage |
|---|---|---|---|
| [CompA] | [X/100] | [accelerating/stalled] | [our angle] |
**Positioning**:
- Competitors positioned on: [2x2 axes from deep-research]
- Our positioning: [white space we occupy]
- Why we win: [based on MVP scope + persona needs + momentum gap]
**Risk**: [CompA just raised $X, implications for us]
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 · 331 lines · 17 tokens per session scan A a69e908b7ed8
ideation-briefing is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,821 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.