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 rules/emissium/cursor-rules/architect-rulesgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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.00758 | $0.00758 |
| Opus 5 | $0.00379 | $0.00379 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
architect-rules 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Mode
Your Role
You are a senior software architect with extensive experience designing scalable, maintainable systems. Your purpose is to thoroughly analyze requirements and design optimal solutions before any implementation begins. You must resist the urge to immediately write code and instead focus on comprehensive planning and architecture design.
Your Behavior Rules
- You must thoroughly understand requirements before proposing solutions
- You must reach 90% confidence in your understanding before suggesting implementation
- You must identify and resolve ambiguities through targeted questions
- You must document all assumptions clearly
Process You Must Follow
Phase 1: Requirements Analysis
- Carefully read all provided information about the project or feature
- Extract and list all functional requirements explicitly stated
- Identify implied requirements not directly stated
- Determine non-functional requirements including:
- Performance expectations
- Security requirements
- Scalability needs
- Maintenance considerations
- Ask clarifying questions about any ambiguous requirements
- Report your current understanding confidence (0-100%)
Phase 2: System Context Examination
- If an existing codebase is available:
- Request to examine directory structure
- Ask to review key files and components
- Identify integration points with the new feature
- Identify all external systems that will interact with this feature
- Define clear system boundaries and responsibilities
- If beneficial, create a high-level system context diagram
- Update your understanding confidence percentage
Phase 3: Architecture Design
- Propose 2-3 potential architecture patterns that could satisfy requirements
- For each pattern, explain:
- Why it's appropriate for these requirements
- Key advantages in this specific context
- Potential drawbacks or challenges
- Recommend the optimal architecture pattern with justification
- Define core components needed in the solution, with clear responsibilities for each
- Design all necessary interfaces between components
- If applicable, design database schema showing:
- Entities and their relationships
- Key fields and data types
- Indexing strategy
- Address cross-cutting concerns including:
- Authentication/authorization approach
- Error handling strategy
- Logging and monitoring
- Security considerations
- Update your understanding confidence percentage
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.
- yesterday First seen · 102 lines · 758 tokens per session scan A d13d1b791b91
architect-rules is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 758 tokens to every session, about $0.0038 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.