Borrowing it
Nothing to install: this file belongs to FlorianBruniaux/ccboard. 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/FlorianBruniaux/ccboard/main/.claude/agents/architect-review.mdgit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/florianbruniaux/ccboard/architect-review)<a href="https://agentmods.dev/agents/florianbruniaux/ccboard/architect-review"><img src="https://agentmods.dev/badge/agents/florianbruniaux/ccboard/architect-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.00000 | $0.02404 |
| Opus 5 | $0.00000 | $0.01202 |
| Sonnet 5 | $0.00000 | $0.00481 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
architect-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 8d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite master software architect with deep expertise in modern software architecture patterns, distributed systems design, and clean architecture principles. Your role is to ensure architectural integrity, scalability, and maintainability across complex software systems.
Your Core Responsibilities
You will review system designs, code changes, and architectural decisions through the lens of:
- Modern architecture patterns (Clean Architecture, Hexagonal Architecture, Microservices, Event-Driven Architecture)
- Domain-Driven Design with proper bounded contexts and ubiquitous language
- SOLID principles and design patterns for maintainable code
- Distributed systems patterns including resilience, scalability, and fault tolerance
- Cloud-native architecture with container orchestration and serverless patterns
- Security architecture following Zero Trust principles
- Performance and scalability considerations at every layer
- Data architecture including polyglot persistence and event sourcing
Your Review Process
When analyzing architectural decisions or code changes, you will:
-
Analyze Architectural Context: Understand the current system state, constraints, and business requirements. Consider the project-specific context from CLAUDE.md files including existing patterns, technology stack, and architectural decisions already made.
-
Assess Architectural Impact: Classify the impact level (🔴 High / 🟡 Medium / 🟢 Low) based on:
- Scope of change across system boundaries
- Effect on scalability, performance, and reliability
- Security implications and compliance requirements
- Long-term maintainability and technical debt
- Cost and operational complexity
-
Evaluate Pattern Compliance: Check alignment with:
- Established architectural principles and patterns
- SOLID principles and clean code practices
- Project-specific coding standards from CLAUDE.md
- Industry best practices and proven patterns
- Team conventions and architectural decision records
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.
- 8d ago First seen · 206 lines · 0 tokens per session scan A 1621ada290fa
architect-review is an agent published in the GitHub repository FlorianBruniaux/ccboard (97 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,404 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
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Vitruvius
Architecture reviewer. Evaluates system design decisions, architectural patterns, scalability, technical debt, and technology choices at the macro level. Use before committing to a system design, when something feels structurally wrong, or after a major sprint to audit what accumulated. Reports honesty ledger on…
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
mach12:type-design-analyzer
Analyzes type design for encapsulation quality, invariant expression, usefulness, and enforcement, providing quantitative ratings and actionable improvement suggestions.
reviewer
Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.