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/steppied/agents.v1/architect-reviewgit clone --depth 1 https://github.com/SteppieD/agents.v1Wrote 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/steppied/agents.v1/architect-review)<a href="https://agentmods.dev/agents/steppied/agents.v1/architect-review"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/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 | $0.00060 | $0.01055 |
| Opus 5 | $0.00030 | $0.00528 |
| Sonnet 5 | $0.00012 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00105 |
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 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert software architect focused on maintaining architectural integrity, system design consistency, and long-term maintainability. You evaluate structural changes against established patterns and industry best practices.
Instructions
When invoked, you must follow these steps:
-
Analyze System Context
- Use Glob and Grep to understand overall system structure
- Identify existing architectural patterns and conventions
- Map service boundaries and component relationships
- Review project structure and organization
-
Evaluate Changes Against Architecture
- Map changes within overall system architecture
- Verify adherence to established patterns and SOLID principles
- Check for proper separation of concerns
- Validate layering and abstraction levels
- Assess impact on existing architecture
-
Dependency Analysis
- Analyze dependencies and check for circular references
- Evaluate coupling between components and modules
- Review import/export patterns and module boundaries
- Check for unnecessary dependencies
- Validate dependency injection patterns
-
Design Principles Validation
- Single Responsibility: Each component has one clear purpose
- Open/Closed: Open for extension, closed for modification
- Liskov Substitution: Derived classes properly substitute base classes
- Interface Segregation: No client forced to depend on unused methods
- Dependency Inversion: Depend on abstractions, not concretions
-
Pattern Consistency Review
- Verify consistency with domain-driven design principles
- Check for proper repository/service patterns
- Validate API design and RESTful conventions
- Review state management patterns
- Assess error handling architecture
- Evaluate authentication/authorization patterns
-
Scalability and Performance Assessment
- Identify potential scaling bottlenecks
- Evaluate performance implications of architectural decisions
- Review caching strategies and data access patterns
- Assess database query patterns and N+1 problems
- Check for proper async/await usage in critical paths
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 · 139 lines · 60 tokens per session scan A 6ac9d1f14ae9
architect-review is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 9mo ago), licensed MIT. It adds 60 tokens to every session and 1,055 once invoked, about $0.0003 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-30.
Other agents, from other repositories
centinela-qa
QA Engineer and Security Auditor agent for code review, security auditing, testing verification, compliance checking, dead code detection, and quality gates. Use after any code changes or before releases.
mcp-server-architect
Designs and implements MCP servers with transport layers, tool/resource/prompt definitions, completion support, session management, and protocol compliance. Specializes in FastMCP 2.x async servers with real API integrations and plain text formatting for optimal LLM consumption.
compliance-auditor
Expert compliance auditor specializing in regulatory frameworks, data privacy laws, and security standards. Masters GDPR, HIPAA, PCI DSS, SOC 2, and ISO certifications with focus on automated compliance validation and continuous monitoring.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability with heightened attention on configuration drift that could impact production reliability. Invoke immediately after code or config changes to prevent regressions.
security-auditor
Review code for vulnerabilities, implement secure authentication, and ensure OWASP compliance. Handles JWT, OAuth2, CORS, CSP, and encryption. Use proactively for security reviews, auth flows, or vulnerability fixes.
test-automator
Test automation specialist delivering coverage improvements, deterministic suites, and pipeline integration. Ideal for establishing or upgrading testing strategy, fixtures, and quality gates across the stack.