Routa is a workspace-based coordination platform for delivering software with multiple AI agents, keeping goals, tasks, sessions, traces, evidence, and review decisions visible on a shared board. It is intended for teams managing agent-assisted development across web and desktop applications. The catalogue contains skills and instructions for working with Routa's delivery workflows.
Borrowing it
Nothing to install: this file belongs to phodal/routa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/phodal/routa/main/.claude/commands/evolution-architecture-review.mdgit clone --depth 1 https://github.com/phodal/routaWrote 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/phodal/routa/evolution-architecture-review)<a href="https://agentmods.dev/commands/phodal/routa/evolution-architecture-review"><img src="https://agentmods.dev/badge/commands/phodal/routa/evolution-architecture-review.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.00010 | $0.00461 |
| Opus 5 | $0.00005 | $0.00230 |
| Sonnet 5 | $0.00002 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
evolution-architecture-review 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 7d 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.
What it actually says
Evolution Architecture Review
FIRST: Load the evolution-architecture-review skill using the Skill tool.
Analyze the repository's architecture evolvability.
Scope from user: $ARGUMENTS
Process
- Create a todo list for discovery, parallel review, synthesis, and final recommendations.
- Read the core architecture and fitness documents identified by the skill.
- Define path exclusions up front. Ignore duplicate or generated trees unless the user explicitly asks for them:
.worktrees/.routa/repos/node_modules/.next/target/out/dist/coverage/tmp/test-results/
- Launch 4 parallel agents with the
Tasktool. Each agent must return only:- concrete findings
- supporting file paths
- top risks
- no speculation without evidence
- no more than 5 findings
- canonical paths from the main repository only
Agent 1: Boundaries
Review module boundaries, ownership seams, dependency direction, and semantic duplication.
Agent 2: Runtime Flow
Review orchestration, lifecycle, task flow, failure handling, tracing, and operational visibility.
Agent 3: Fitness
Review tests, hard gates, parity checks, contracts, and other executable architecture constraints.
Agent 4: Evolution Path
Review where the system can evolve incrementally, what to avoid, and what smallest safe next steps exist.
- Read any additional files needed to verify high-signal findings from the agents.
- Remove duplicate findings caused by mirrored paths or equivalent evidence.
- Synthesize the result into one architecture review.
Output Requirements
- Use the structure defined in the skill.
- Separate facts from inferences.
- Prefer incremental evolution recommendations.
- Suggest concrete fitness functions when gaps exist.
- Cite repository paths for every major claim.
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.
- 7d ago First seen · 61 lines · 10 tokens per session scan A ebd7b4e134e5
evolution-architecture-review is a command published in the GitHub repository phodal/routa (1,809 stars, last pushed 24d ago), licensed MIT. It adds 10 tokens to every session and 461 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.