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/goranerhartic/cursor-development-rules/architecturegit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/architecture)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/architecture"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/architecture.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.00036 | $0.00387 |
| Opus 5 | $0.00018 | $0.00193 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
architecture 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 today.
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.
What it actually says
Architecture Principles
Preferred Patterns
Vertical Slice Architecture
- Organize by feature, not by technical layer
- Each slice contains its own command/query, handler, validator, and entities
- Minimize cross-slice dependencies
Clean Architecture
- Domain — Entities, Value Objects, Domain Events (no dependencies)
- Application — Use cases, interfaces, DTOs (depends on Domain)
- Infrastructure — Data access, external services (implements interfaces)
- API — Controllers/endpoints, middleware/filters (composition root)
CQRS (Command Query Responsibility Segregation)
- Separate read (queries) from write (commands) operations
- Use mediator or dispatcher pattern for routing
- Commands return
Result<T>, queries return DTOs
Domain-Driven Design
- Aggregates — Consistency boundaries with single root
- Value Objects — Immutable, equality by value
- Domain Events — Publish for cross-aggregate communication
Design Principles
| Principle | Application |
|---|---|
| SOLID | Single Responsibility, Open/Closed, Liskov, Interface Segregation, Dependency Inversion |
| DRY | Extract common logic; avoid premature abstraction |
| KISS | Prefer straightforward solutions over clever ones |
| YAGNI | Don't build features speculatively |
Layering Guidelines
- Dependencies flow inward (outer layers depend on inner, never reverse)
- Domain layer has no external dependencies
- Infrastructure implements domain interfaces
- API layer orchestrates, doesn't contain business logic
See also: Language-specific implementations in languages/*/ folders
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.
- today First seen · 47 lines · 36 tokens per session scan A dbcc979223d1
architecture is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 387 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-09-03.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.