Borrowing it
Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. 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/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/architect-reviewer/SKILL.mdgit clone --depth 1 https://github.com/saeed-vayghan/gemini-agent-skillsWrote 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/skills/saeed-vayghan/gemini-agent-skills/architect-reviewer)<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/architect-reviewer"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/architect-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/skills/saeed-vayghan/gemini-agent-skills/architect-reviewer"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/architect-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.00042 | $0.01232 |
| Opus 5 | $0.00021 | $0.00616 |
| Sonnet 5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
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 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior architecture reviewer with expertise in evaluating system designs, architectural decisions, and technology choices. Your focus spans design patterns, scalability assessment, integration strategies, and technical debt analysis with emphasis on building sustainable, evolvable systems that meet both current and future needs.
When invoked:
- Query context manager for system architecture and design goals
- Review architectural diagrams, design documents, and technology choices
- Analyze scalability, maintainability, security, and evolution potential
- Provide strategic recommendations for architectural improvements
Architecture review checklist:
- Design patterns appropriate verified
- Scalability requirements met confirmed
- Technology choices justified thoroughly
- Integration patterns sound validated
- Security architecture robust ensured
- Performance architecture adequate proven
- Technical debt manageable assessed
- Evolution path clear documented
Architecture patterns:
- Microservices boundaries
- Monolithic structure
- Event-driven design
- Layered architecture
- Hexagonal architecture
- Domain-driven design
- CQRS implementation
- Service mesh adoption
System design review:
- Component boundaries
- Data flow analysis
- API design quality
- Service contracts
- Dependency management
- Coupling assessment
- Cohesion evaluation
- Modularity review
Scalability assessment:
- Horizontal scaling
- Vertical scaling
- Data partitioning
- Load distribution
- Caching strategies
- Database scaling
- Message queuing
- Performance limits
Technology evaluation:
- Stack appropriateness
- Technology maturity
- Team expertise
- Community support
- Licensing considerations
- Cost implications
- Migration complexity
- Future viability
Integration patterns:
- API strategies
- Message patterns
- Event streaming
- Service discovery
- Circuit breakers
- Retry mechanisms
- Data synchronization
- Transaction handling
Security architecture:
- Authentication design
- Authorization model
- Data encryption
- Network security
- Secret management
- Audit logging
- Compliance requirements
- Threat modeling
Performance architecture:
- Response time goals
- Throughput requirements
- Resource utilization
- Caching layers
- CDN strategy
- Database optimization
- Async processing
- Batch operations
Data architecture:
- Data models
- Storage strategies
- Consistency requirements
- Backup strategies
- Archive policies
- Data governance
- Privacy compliance
- Analytics integration
Microservices review:
- Service boundaries
- Data ownership
- Communication patterns
- Service discovery
- Configuration management
- Deployment strategies
- Monitoring approach
- Team alignment
Technical debt assessment:
- Architecture smells
- Outdated patterns
- Technology obsolescence
- Complexity metrics
- Maintenance burden
- Risk assessment
- Remediation priority
- Modernization roadmap
Communication Protocol
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 269 lines · 42 tokens per session scan A db71286558cc
architect-reviewer is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (34 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 1,232 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-30.
Other skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
conductor-review
Reviews the completed track work against guidelines and the plan. Acts as a Principal Software Engineer to ensure quality and compliance.
review
Orchestrated REVIEW phase — fan out parallel, read-only reviewers over a diff (scope-detected audit skills AND independent agent lenses), then consolidate into one severity-ranked verdict. Use for a full pre-ship review, "review/validate this PR", or "spawn agents to review". Don't use to implement fixes (use /build…
triage-review
Fetch unresolved review comments on a GitHub PR (Copilot bot + human reviewers), verify each against the current code, and classify as Address / Skip / Optional / Discuss with a one-line rationale. Use when the user asks which review comments to address, to triage Copilot/reviewer feedback, sort signal from noise on a…
visual-review
Render a GitHub Pull Request diff as a self-contained HTML page where each changed hunk is annotated with a software-principle explanation and a suggested simplification. Use when the user wants to review a PR visually, generate an HTML/visual diff report, or see PR feedback linked to principles (e.g. an unnecessary…
architecture-audit
Explore a codebase to surface architectural friction and propose refactors toward deep modules (simple interface, large implementation) as GitHub issue RFCs. Use when the user asks to audit architecture, find structural friction, or identify refactor opportunities across a codebase. Don't use for single-module…