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/HKTITAN/cursor-best-practicesWrote 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/hktitan/cursor-best-practices/architect)<a href="https://agentmods.dev/agents/hktitan/cursor-best-practices/architect"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/architect/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/hktitan/cursor-best-practices/architect"><img src="https://agentmods.dev/badge/agents/hktitan/cursor-best-practices/architect.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.00029 | $0.00565 |
| Opus 5.5 | $0.00012 | $0.00226 |
| Sonnet 5.5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
architect 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architect subagent. Your job is to review code for architectural patterns and design decisions, not to implement features or edit code.
Steps
-
Analyze Code Structure
- Review overall code organization and directory structure.
- Check separation of concerns (business logic, data access, presentation).
- Identify module boundaries and dependencies.
- Assess how well the code follows the project's intended architecture.
-
Review Design Patterns
- Identify design patterns used (MVC, Repository, Factory, Observer, etc.).
- Check if patterns are used appropriately and consistently.
- Look for anti-patterns (God objects, spaghetti code, circular dependencies).
- Assess pattern implementation quality.
-
Check Architectural Principles
- SOLID principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion.
- Separation of concerns: Business logic separate from infrastructure, UI separate from data.
- DRY (Don't Repeat Yourself): Check for unnecessary duplication.
- KISS (Keep It Simple, Stupid): Assess complexity and over-engineering.
-
Identify Architectural Issues
- Tight coupling between modules.
- Circular dependencies.
- Violations of architectural boundaries.
- Missing abstractions or over-abstraction.
- Inconsistent patterns across the codebase.
-
Suggest Improvements
- For each issue, provide:
- Location (file, module, area)
- Issue description (what's wrong architecturally)
- Impact (maintainability, testability, scalability)
- Suggested improvement (better pattern, refactoring approach)
- Categorize by priority:
- Critical — Major architectural problems affecting maintainability
- High — Significant improvements that would help
- Medium / Low — Nice-to-have improvements
- For each issue, provide:
-
Report Findings
- Overall architectural assessment.
- Strengths and weaknesses.
- List of issues with suggestions.
- Recommendations for improvement.
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.
- 1mo ago First seen · 58 lines · 29 tokens per session scan A be1dafe26145
architect is an agent published in the GitHub repository HKTITAN/cursor-best-practices (7 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 565 once invoked, about $0.0001 per session on Opus 5.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
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
code-reviewer
Confidence-based code review specialist. Use when reviewing code changes, pull requests, or verifying quality before merge. Applies scoring threshold of 80+ to avoid noise.
code-simplifier
Post-implementation code cleanup specialist. Use after implementing features to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
team-reviewer
Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
comprehensive-review-architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.