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.
npx agentmods add commands/thewaywithin/agent-11/architectgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/architect)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/architect"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/architect.svg" alt="Measured on agentmods" 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.00012 | $0.11129 |
| Opus 5 | $0.00006 | $0.05565 |
| Sonnet 5 | $0.00002 | $0.02226 |
| Haiku 4.5 | $0.00001 | $0.01113 |
Grade A, and why
architect 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 today.
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 — 1,371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect Command
PURPOSE
Generate a comprehensive architecture.md document that captures all system design decisions before project planning begins. This bridges the gap between "what to build" (PRD) and "how to build it" (project-plan.md).
Why This Matters: PRDs define features but often hand-wave technical decisions. Architecture documentation ensures:
- Tech stack decisions are explicit and justified
- Integration patterns are defined before coding
- Data models are designed before implementation
- Security and scalability are addressed upfront
- Trade-offs are documented for future reference
WORKFLOW POSITION
/foundations init → /architect → /bootstrap → /coord continue
↓ ↓ ↓ ↓
Extract PRD Design System Create Plan Build It
/architect is REQUIRED before /bootstrap - you can't plan tasks without knowing the architecture.
PREREQUISITES
Before running /architect, ensure:
-
/foundations inithas completed successfully.context/structured/prd.yamlexists (REQUIRED).context/structured/vision.yamlexists (recommended).context/structured/roadmap.yamlexists (optional - provides strategic context)
-
PRD contains tech stack hints
- Frontend framework mentioned
- Database preference indicated
- Key integrations identified
Context Sources Used:
prd.yaml→ Features, tech stack preferences, integrationsvision.yaml→ Hedgehog concept, value proposition (informs architectural priorities)roadmap.yaml→ Keystone products, implementation framework (informs build sequence)
EXECUTION PROTOCOL
CRITICAL: This command MUST prompt for mode selection before doing any work (unless --mode flag is provided).
Step 1: Check for --mode Flag
If --mode auto → Skip to AUTO MODE section
If --mode engaged → Skip to ENGAGED MODE section
If no --mode flag → Continue to Step 2
Step 2: Present Mode Selection (MANDATORY)
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.
- today First seen · 1,371 lines · 12 tokens per session scan A d7c7027fb3c7
architect is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d ago), licensed MIT. It adds 12 tokens to every session and 11,129 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-09-04.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
brainstorm
Facilitate a structured brainstorming session for feature development using Scrum Master techniques.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.