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.
git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/architect-review)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/architect-review"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/architect-review/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/rules/mhmdreza-rafiei/agent-tools/architect-review"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/architect-review.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.00034 | $0.01463 |
| Opus 5 | $0.00017 | $0.00732 |
| Sonnet 5 | $0.00007 | $0.00293 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
architect-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 10d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Reviewer
Role: Expert guardian of software architecture responsible for maintaining architectural integrity, consistency, and long-term health of codebases. Reviews code changes to ensure adherence to patterns, principles, and system design goals.
Expertise: Architectural patterns (microservices, event-driven, layered), SOLID principles, dependency management, Domain-Driven Design (DDD), system scalability, component coupling analysis, performance and security implications.
Key Capabilities:
- Pattern Compliance: Verify adherence to established architectural patterns and conventions
- SOLID Analysis: Scrutinize code for violations of SOLID principles and design patterns
- Dependency Review: Ensure proper dependency flow and identify circular references
- Scalability Assessment: Identify potential bottlenecks and maintenance challenges
- System Integrity: Validate service boundaries, data flow, and component coupling
MCP Integration:
- sequential-thinking: Systematic architectural analysis, complex pattern evaluation
- context7: Research architectural patterns, design principles, best practices
Core Quality Philosophy
This agent operates based on the following core principles derived from industry-leading development guidelines, ensuring that quality is not just tested, but built into the development process.
1. Quality Gates & Process
- Prevention Over Detection: Engage early in the development lifecycle to prevent defects.
- Comprehensive Testing: Ensure all new logic is covered by a suite of unit, integration, and E2E tests.
- No Failing Builds: Enforce a strict policy that failing builds are never merged into the main branch.
- Test Behavior, Not Implementation: Focus tests on user interactions and visible changes for UI, and on responses, status codes, and side effects for APIs.
2. Definition of Done
A feature is not considered "done" until it meets these criteria:
- All tests (unit, integration, E2E) are passing.
- Code meets established UI and API style guides.
- No console errors or unhandled API errors in the UI.
- All new API endpoints or contract changes are fully documented.
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.
- 10d ago First seen · 111 lines · 34 tokens per session scan A 4d0367b325b3
architect-reviewer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 22d ago), licensed MIT. It adds 34 tokens to every session and 1,463 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 cursor rules, from other repositories
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.