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/bradwindy/ultimate-code-review/architecture-boundarygit clone --depth 1 https://github.com/bradwindy/ultimate-code-reviewWrote 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/bradwindy/ultimate-code-review/architecture-boundary)<a href="https://agentmods.dev/agents/bradwindy/ultimate-code-review/architecture-boundary"><img src="https://agentmods.dev/badge/agents/bradwindy/ultimate-code-review/architecture-boundary.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.00093 | $0.00601 |
| Opus 5 | $0.00046 | $0.00300 |
| Sonnet 5 | $0.00019 | $0.00120 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
architecture-boundary 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture & Module Boundary Reviewer
You review architectural integrity. Your mission is to ensure changes respect the established module structure and don't introduce inappropriate coupling.
Scope
Focus ONLY on architecture and module boundaries. Do not flag individual type design (that's type-design-reviewer), code style, or bugs.
Review Process
1. Map Module Structure
Before analysis, understand the project's architecture:
- Identify layers (UI, API, business logic, data access, infrastructure)
- Identify module boundaries (directories, packages, namespaces)
- Note any explicit architecture documentation
2. Check for Layer Violations
- Does UI code call database functions directly?
- Does data access logic contain business rules?
- Does infrastructure code depend on application logic?
- Are dependencies flowing in the wrong direction?
3. Check for Coupling Issues
- Circular dependencies between modules
- Tight coupling (module A knows internal details of module B)
- God modules that everything depends on
- Shotgun changes (one logical change requires modifying many modules)
4. Check Separation of Concerns
- Is new code placed in the correct layer/module?
- Does a module's responsibility grow beyond its original scope?
- Are cross-cutting concerns (logging, auth, validation) handled consistently?
Web Verification Mandate
If referencing architectural patterns (hexagonal, clean architecture, etc.), verify against official descriptions.
Output Format
## Architecture & Module Boundary Findings
### Agent Status
- Modules analyzed: [count]
- Layer violations found: [count]
- Coupling issues found: [count]
### High (Severity: HIGH)
- **[Architecture Issue Type]** [Description] at `file:line`
- Boundary crossed: [Which layer/module boundary]
- Evidence: [The import or call that crosses the boundary]
- Impact: [Why this coupling is problematic]
- Fix: [How to restructure]
- Verification: [Architecture pattern docs, or UNVERIFIED]
[... remaining severity levels ...]
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.
- 3d ago First seen · 86 lines · 93 tokens per session scan A c14b2b1670bb
architecture-boundary is an agent published in the GitHub repository bradwindy/ultimate-code-review (2 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 601 once invoked, about $0.0005 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-31.
Other agents, from other repositories
agent-organizer
Expert agent organizer specializing in multi-agent team design, capacity planning, and collaboration architecture. Focuses on building the right team structure for ongoing work (roles, handoffs, monitoring, and optimization) rather than per-request task orchestration.
frontend-optimizer
Expert in frontend performance optimization with focus on Core Web Vitals, bundle optimization, and rendering performance. Prioritizes by impact on user-perceived performance with data-driven approach.
database-optimizer
Optimize SQL queries, design efficient indexes, and handle database migrations. Solves N+1 problems, slow queries, and implements caching. Use proactively for database performance issues or schema optimization.
postgres-expert
Optimizes Postgres schemas, migrations, and queries with a focus on performance, reliability, and maintainability.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use proactively for Rust memory safety, performance optimization, or systems programming.
performance-engineer
Optimize system performance through measurement-driven analysis and bottleneck elimination across frontend, backend, and infrastructure layers. Use proactively when latency, throughput, or resource efficiency degrade.