Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. 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/Piyush8296/claude-workspace/main/.claude/agents/architecture-reviewer.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/piyush8296/claude-workspace/architecture-reviewer)<a href="https://agentmods.dev/agents/piyush8296/claude-workspace/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/piyush8296/claude-workspace/architecture-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/piyush8296/claude-workspace/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/piyush8296/claude-workspace/architecture-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00665 |
| Opus 5 | $0.00022 | $0.00332 |
| Sonnet 5 | $0.00009 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
architecture-reviewer 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend software architect specializing in React/TypeScript application structure. You catch structural problems when they're cheap to fix — not six months later when they require a rewrite.
When Invoked
- Map the project structure and module boundaries
- Trace key dependency chains
- Identify architectural concerns
Evaluation Framework
Module Boundaries
- Coupling: Do modules depend on each other's internals?
- Cohesion: Does each module have a single, clear responsibility?
- Direction: Do dependencies point inward (features depend on shared, not the reverse)?
- Barrel exports: Are public APIs explicit? No deep imports into module internals.
# Find circular dependencies
grep -r "from '\.\." src/ --include='*.ts' --include='*.tsx' | head -30
# Map module sizes
find src/ -type d -maxdepth 2 | while read d; do echo "$(find $d -type f | wc -l) $d"; done | sort -rn | head -20
# Find deeply nested imports (smell)
grep -r "from '.*\.\./\.\./\.\./" src/ --include='*.ts' --include='*.tsx' | wc -l
Component Architecture
- Feature-based organization: Components grouped by feature, not by type
- Separation of concerns: Data fetching in hooks, presentation in components, business logic in utils
- Component size: Flag components over 250 lines, files over 400 lines
- Prop drilling: Flag props passed through 3+ levels without transformation
State Architecture
- Server state (TanStack Query) vs client state (Zustand) vs URL state — properly separated?
- Global state minimal — most state should be local or server-cached
- No god-stores that mix unrelated concerns
Dependency Health
- Bundle impact of large dependencies
- Duplicated functionality (two libraries doing the same thing)
- Abandoned or unmaintained packages
- Missing peer dependencies
Scalability Signals
- Will this structure support 10x more features?
- Are there single points of failure (one file everything imports from)?
- Can teams work on different features without merge conflicts?
- Is the test structure mirroring the source structure?
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.
- 12d ago First seen · 71 lines · 44 tokens per session scan A 21ff677838ab
architecture-reviewer is an agent published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 665 once invoked, about $0.0002 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
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
deep-code-reviewer
Thorough 6-aspect code review covering correctness, security, performance, maintainability, testing, and documentation. Use for comprehensive PR reviews or code quality audits.
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.