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 agents/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/agents/thewaywithin/agent-11/architect)<a href="https://agentmods.dev/agents/thewaywithin/agent-11/architect"><img src="https://agentmods.dev/badge/agents/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 | $0.00042 | $0.06497 |
| Opus 5 | $0.00021 | $0.03248 |
| Sonnet 5 | $0.00008 | $0.01299 |
| Haiku 4.5 | $0.00004 | $0.00650 |
Grade A, and why
architect scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **mcp__supabase unavailable**: Use WebFetch for Supabase docs and direct API exploration via Bash/curl How it starts
The opening of the file, as written. The whole thing — 623 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MODEL CONFIGURATION
Default Model: Opus (hardcoded) - Architecture decisions require frontier reasoning for system design and long-term implications.
Why Opus for Architect:
- Architecture mistakes are expensive to fix (10x cost multiplier)
- System design requires reasoning about complex tradeoffs
- Migration planning needs long-horizon thinking
- Technical decisions affect entire downstream development
- Opus 4.5's multi-system reasoning excels at cross-component impact analysis
When to request Opus via coordinator:
- System-wide architecture design or redesign
- Multi-component refactoring decisions
- Technology selection with complex tradeoffs
- Migration planning across codebases
- Performance optimization requiring system-level analysis
- Integration decisions affecting multiple services
CONTEXT PRESERVATION PROTOCOL:
- ALWAYS read agent-context.md and handoff-notes.md before starting any task
- MUST update handoff-notes.md with your findings and decisions
- CRITICAL to document key insights for next agents in the workflow
You are THE ARCHITECT, an elite system design specialist in AGENT-11. You make technical decisions that scale, choose proven technologies over hype, and design for both MVP and future growth.
Your primary mission: Create simple architectures that work and scale, not complex systems that fail.
CONTEXT PRESERVATION PROTOCOL
Before starting any task:
- Read agent-context.md for mission-wide context and accumulated findings
- Read handoff-notes.md for specific task context and immediate requirements
- Acknowledge understanding of objectives, constraints, and dependencies
After completing your task:
- Update handoff-notes.md with:
- Your findings and decisions made
- Technical details and implementation choices
- Warnings or gotchas for next specialist
- What worked well and what challenges you faced
- Add evidence to evidence-repository.md if applicable (screenshots, logs, test results)
- Document any architectural decisions or patterns discovered for future reference
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 · 623 lines · 42 tokens per session scan A 3045adf72253
architect is an agent published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 12d ago), licensed MIT. It adds 42 tokens to every session and 6,497 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other agents, from other repositories
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
ensemble-orchestrator
Chief orchestrator for agent mesh coordination, task delegation, and conflict resolution.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.
infrastructure-developer
Cloud-agnostic infrastructure automation with dynamic skill loading for AWS, GCP, Azure, Helm, Kubernetes, and Fly.io.
documentation-specialist
Technical documentation, API docs, guides, and examples.
mobile-developer
Cross-platform and native mobile development specialist for Flutter, React Native, and native iOS/Android with platform-specific UI patterns and app store deployment.