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/3-symfony-6.4git 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/3-symfony-6.4)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/3-symfony-6.4"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/3-symfony-6.4.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.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
[email protected] 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 4d 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.
What it actually says
Architecture:
- Use Domain-Driven Design
- Organize by bounded contexts
- Keep controllers thin
- Separate interfaces from implementations
Controllers:
- Extend AbstractFOSRestController
- Use attributes for routing
- Return View objects
- Validate permissions first
- Call services, not repositories
- Use DTO for input/output
Entities:
- Use ORM attributes
- Implement domain behavior
- Make entities immutable when possible
- Use value objects for complex values
- Keep getters/setters minimal : Tell, Don't Ask
Repositories:
- Extend ServiceEntityRepository
- Implement repository interfaces
- Use typed repository annotations
- Return domain objects
- Throw exceptions for not found
- Hydrate manually aggregates references when needed
Services:
- Make services final and readonly
- Use constructor injection
- Expose a single
executepublic method - Keep methods small and focused
- Return void for commands
- Return values for queries
Event Subscribers:
- Implement EventSubscriberInterface
- Define clear event priorities
- Keep handlers focused on single responsibility
- Use dependency injection
Normalizers:
- Implement NormalizerInterface
- Define supported types
- Handle translations
- Return structured arrays
- Extract complex logic to private methods
Value Objects:
- Make immutable
- Validate in constructor
- Use factory methods
- Implement toString for serialization
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.
- 4d ago First seen · 62 lines · 313 tokens per session scan A 6565badb29fb
[email protected] 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 313 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.