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/cmnemoi/cursor-rules/001-feature-based-architecturegit clone --depth 1 https://github.com/cmnemoi/cursor-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/cmnemoi/cursor-rules/001-feature-based-architecture)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/001-feature-based-architecture"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/001-feature-based-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.00000 | $0.03247 |
| Opus 5 | $0.00000 | $0.01623 |
| Sonnet 5 | $0.00000 | $0.00649 |
| Haiku 4.5 | $0.00000 | $0.00325 |
Grade A, and why
001-feature-based-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 3d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Standards
1.2.0
Context
- These rules apply to the overall architecture of applications in the monorepo
- They ensure proper separation of concerns
- They promote testability and maintainability
- Backend follows a Domain-Driven Design Clean Architecture approach (Entity/Domain, Repository, Service, Controller)
- Frontend follows Feature-based Architecture principles with Vue components
Backend Architecture (Clean Architecture)
Layers
- Separate code into distinct layers: Entity/Domain, Repository, Service, Controller
- Ensure dependencies inversion between Repository and Service layer (Service → RepositoryInterface → Repository)
- Keep the Domain layer independent of frameworks and external concerns
- Use interfaces to define boundaries between layers
Entity/Domain Layer
- Focus on business entities and logic
- Keep domain models pure and framework-independent
- Define value objects for complex value types
- Define repository interfaces in the domain layer
- Include enum classes to represent domain constants
- Use ValueObject classes to represent complex immutable values
Service Layer
- Implement use cases that orchestrate domain logic
- Service classes should be focused on a single responsibility
- Define service interfaces to allow for dependency inversion
- Use DTOs for data transfer between layers
- Implement proper validation at this layer
Repository Layer
- Implement repository interfaces defined in the domain layer
- Handle data persistence concerns
- Keep infrastructure details isolated from business logic
- Define repository interfaces that match domain needs
Controller Layer
- Focus on API concerns and request/response handling
- Keep presentation logic separate from business logic
- Use controllers to handle HTTP requests
- Implement proper error handling and response formatting
- Return appropriate HTTP status codes based on operation results
Testing Approach
- Write unit tests using in-memory implementations of repositories
- Use the "Given-When-Then" pattern to structure tests
- Create functional tests for end-to-end testing with real infrastructure
- Follow TDD methodology to ensure proper test coverage
- Write tests that test behavior, not implementation details
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.
- 3d ago First seen · 469 lines · 3,247 tokens per session scan A e33196384780
001-feature-based-architecture is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,247 tokens. 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.
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.