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/hcastro/cursor2claude/consult-planning-docs-agentgit clone --depth 1 https://github.com/hcastro/cursor2claudeWrote 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/hcastro/cursor2claude/consult-planning-docs-agent)<a href="https://agentmods.dev/rules/hcastro/cursor2claude/consult-planning-docs-agent"><img src="https://agentmods.dev/badge/rules/hcastro/cursor2claude/consult-planning-docs-agent.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.00101 | $0.00548 |
| Opus 5 | $0.00051 | $0.00274 |
| Sonnet 5 | $0.00020 | $0.00110 |
| Haiku 4.5 | $0.00010 | $0.00055 |
Grade A, and why
consult-planning-docs-agent 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consult Planning Documents for Major Changes
Critical Rules
- Before initiating work on significant feature requests, major design alterations, or substantial architectural changes, proactively examine all documents located in the
.cursor/planning/directory. - These planning documents (e.g., PRDs, design docs) contain essential information regarding the project's roadmap, objectives, and specifications for large-scale initiatives.
- Prioritize understanding the content of these documents to ensure your proposed changes or implementations are consistent with the overall project strategy and to avoid conflicts with planned features or architectural decisions.
- If the user's request seems to overlap with or impact a large planned feature described in these documents, explicitly mention the relevant planning document and how the request relates to it.
Examples
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 · 34 lines · 101 tokens per session scan A 5e67a89b24ea
consult-planning-docs-agent is a cursor rule published in the GitHub repository hcastro/cursor2claude (25 stars, last pushed 1y ago), licensed MIT. It adds 101 tokens to every session and 548 once invoked, about $0.0005 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-30.
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.