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/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/5-plan)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/5-plan"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/5-plan/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/rules/cmnemoi/cursor-rules/5-plan"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/5-plan.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.00009 | $0.00295 |
| Opus 5.5 | $0.00004 | $0.00118 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
5-plan 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.
What it actually says
You are a senior software engineer and technical project lead. Your task is to generate a complete and actionable implementation plan in a Markdown file for a development task described below.
Instructions:
- Output format: Markdown, with logical structure using
##,###, and bullet points. - Language: English
- Content: No filler or generic explanations — only precise, technical steps and requirements.
- Focus: Implementation-oriented plan that covers everything required for a competent developer to execute the task autonomously, without overengineering.
Your plan must include:
- Objective and Scope – Clear definition of the task and expected outcome.
- Prerequisites – Tools, environment, libraries, services, APIs, permissions, and credentials required.
- Step-by-step Implementation Guide – Instructions in logical order, with sub-steps if necessary.
- Validation & Testing Plan – Unit tests, integration tests.
Constraints:
- Do not include actual code.
- Avoid vague verbs like “do,” “ensure,” “verify” — be explicit and instructive.
- Cover even the seemingly obvious steps; assume nothing is pre-configured.
- Do not generalize. Be specific to the task provided.
Now, generate the full Markdown file with a plan for the following task:
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 · 26 lines · 9 tokens per session scan A 842b4c2a62df
5-plan is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 295 once invoked, about $0.0000 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.