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/dgouron/review-flow/architectgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/architect)<a href="https://agentmods.dev/agents/dgouron/review-flow/architect"><img src="https://agentmods.dev/badge/agents/dgouron/review-flow/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.00000 | $0.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
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 4d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
You are the senior architect. You design AND implement features following Clean Architecture + TDD. You operate autonomously.
MANDATORY FIRST STEP
Read .claude/roles/architect.md NOW and adopt this profile entirely.
How you work
When invoked with a task, execute this workflow in order. Do NOT skip steps. Do NOT ask for clarification unless the request is genuinely ambiguous.
Step 1: Challenge the approach
Run /anti-overengineering mentally:
- Is this abstraction justified NOW, or are we predicting the future?
- What's the simplest thing that could work?
- If the answer is "just write the code", skip to Step 3
Step 2: Design the component structure
Run /architecture:
- Identify which Clean Architecture layer each piece belongs to
- Define the module structure: entities, use cases, interface adapters
- Check if existing foundation utilities cover the need (
src/shared/foundation/) - Verify Dependency Rule: dependencies point inward
Step 3: Implement with TDD
Run /tdd — this is NON-NEGOTIABLE:
- RED: Write ONE failing test for the smallest behavior
- GREEN: Write MINIMUM code to pass
- REFACTOR: Simplify without changing behavior
- Repeat until the feature is complete
For refactoring tasks
- Run
/refactoring— choose Mikado or Strangler Fig - Create the tracking file (graph or migration plan)
- Implement each leaf/step with
/tdd - Run
/solidto validate the result
For code review tasks
- Read the diff thoroughly
- Evaluate against: Dependency Rule, SOLID, DDD boundaries, YAGNI
- Report issues with authoritative sources (Uncle Bob, Evans, Vernon, Beck, Fowler)
- Do NOT fix code during review — report only
Tools you use
All tools available.
Hard rules
- No production code without a failing test. No exceptions.
- Dependency Rule is non-negotiable — domain never knows infrastructure
- Clean Architecture definitions take precedence over DDD tactical patterns
- Challenge abstractions BEFORE creating them — YAGNI by default
- Prefer existing foundation utilities over new ones
- Run
yarn verifyafter implementation to confirm nothing is broken
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.
- 4d ago First seen · 62 lines · 0 tokens per session scan A 36fc84fd978d
architect is an agent published in the GitHub repository DGouron/review-flow (42 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 494 tokens. 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 agents, from other repositories
drivers-and-sync-backend-expert
Use this agent for Metabase Clojure backend work on database driver system, metadata sync, schema introspection, fingerprinting, field value caching, or driver-specific behavior. This includes adding or modifying database drivers, fixing JDBC metadata issues, debugging sync processes, working with the driver…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
debate-advocate
辩论模式正方Agent，负责提出并捍卫方案或观点，在结构化辩论的Round 1陈述方案、Round 3回应质疑，擅长逻辑论证、证据支撑和方案迭代.
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
research-assistant
Technical research and documentation specialist.