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/markmhendrickson/foundation/plan_detectiongit clone --depth 1 https://github.com/markmhendrickson/foundationWhat 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.00030 | $0.00597 |
| Opus 5 | $0.00015 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
plan_detection 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 yesterday.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Creation Detection Rule
Reference: foundation/development/plan_workflow.md — Complete workflow
This is a foundation rule. Configuration is read from foundation-config.yaml.
Trigger Patterns
When a user mentions any of the following patterns, automatically detect plan creation intent:
- "create plan" / "new plan" / "add plan"
- "create feature" / "new feature" / "implement feature"
- "we need to" / "we should" / "let's build" (when describing new work)
- Planning discussions about new functionality or changes
- Requests to track a decision, goal, or initiative
Agent Actions
Step 1: Detection and Confirmation
If context suggests plan creation:
-
Load configuration:
- Read
foundation-config.yamlto get plans settings - Check if
plans.enabledis true
- Read
-
Extract plan information from context:
- Title or description of what to plan
- Priority hints (P0/P1/P2/P3)
- Scope hints (what functionality is mentioned)
- Related entities (releases, objectives, other plans)
-
Ask for confirmation:
I see you're describing new work. Should I create a plan in Neotoma following the plan creation workflow? (yes/no) -
Exception handling:
- If user says "no" → do not proceed
- If user says "just a note" → store as a
noteentity instead
Step 2: Execute Plan Creation Workflow
If user confirms (yes):
-
Load required documents:
foundation/development/plan_workflow.md(primary workflow)- Skill
create-plan(.cursor/skills/create-plan/SKILL.md)
-
Follow the plan creation workflow:
- Collect required fields (title, description, scope, out_of_scope, success_criteria)
- Run alignment check
- Store plan entity in Neotoma
- Create relationships to related entities
Constraints
- Do NOT proceed without user confirmation — always ask before creating plans
- Do NOT create plans as markdown files in a repo directory — store in Neotoma
- Plans are mirrored to
plans/automatically; do not edit mirror files directly - Always get user confirmation that the plan summary matches their intent
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.
- yesterday First seen · 75 lines · 30 tokens per session scan A c2f7f1bf5df8
plan_detection is a cursor rule published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 597 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-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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.