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/competitive-threat)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/competitive-threat"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/competitive-threat/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/competitive-threat"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/competitive-threat.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.00013 | $0.02955 |
| Opus 5 | $0.00006 | $0.01477 |
| Sonnet 5 | $0.00003 | $0.00591 |
| Haiku 4.5 | $0.00001 | $0.00296 |
Grade A, and why
competitive-threat 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:competitive-threat
Trigger
/architect:competitive-threat — Run to analyze specific competitive threats or at any time to stay ahead of market movements.
Prerequisite: Should run after /architect:deep-research (needs competitor list + market context).
Optional intensity levels:
- Quick: 1 hour, focus on top 3 competitors
- Standard: 2-3 hours, analyze top 5 competitors + market leaders
- Deep: 4+ hours, comprehensive threat assessment + scenario planning
Purpose
Identify emerging competitive threats beyond current feature comparison. Reveals:
- What competitors are building next (funding, hiring, roadmap signals)
- Who's winning and why (strategic moves, market consolidation)
- Existential risks (incumbent response, well-funded entrants)
- What could kill us and how to address it
Different from deep-research: deep-research is landscape (market sizing, features, pricing), competitive-threat is threat detection (momentum, strategic moves, risk assessment).
Workflow
Step 1: Gather Context
Load competitor list from previous research:
Read: architecture-output/deep-research.md (competitor list, market sizing)
Read: architecture-output/_state.json (momentum scores, feature parity)
Read: architecture-output/mvp-scope.md (our differentiation, timeline)
Identify: Which competitors are the real threats? (Usually top 3, ranked by momentum score)
Step 2: Load Skills
Load:
- deep-research skill — for verification methodology
- founder-communication skill — for risk communication
Step 3: Strategic Moves Research (Phase 1 — Discover)
Use WebSearch to find signals of competitive strategy:
Funding & Consolidation (run 5+ searches):
"{top competitor}" Series A / Series B / Series C funding round"{competitor}" IPO acquisition investment 2024 2025"{market leader}" acquires {adjacent category} 2024"startup funding {product category}" 2024 2025
Hiring & Talent (run 3+ searches):
"{competitor}" hiring engineering 2025 site:linkedin.com"{competitor}" jobs careers "machine learning" OR "AI""heading to {competitor}" job change site:linkedin.com(signals who joined)
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 · 324 lines · 13 tokens per session scan A b3af754a2ca8
competitive-threat is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,955 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.