agentmods.dev

foundation: Skill for Cursor

.cursor/skills/create-plan/SKILL.md

create-plan is a skill for Cursor from markmhendrickson/foundation. It costs 25 tokens per session (686 once invoked), scanned A, a copy of create-plan, MIT.

A workflow for creating a new plan as a Neotoma record. It collects the plan's goals, scope, success measures, and status, then can link it to related project records.

In plain words
What is it for?
Use it to create plans, check that their summary matches the intended work, connect them to objectives or releases, and optionally rebuild the plans mirror.
Why use it?
It turns an informal idea into a structured plan with clear boundaries and measurable completion criteria.

Skill for Cursor

Written for Cursor: installed under .cursor/.

This is markmhendrickson/foundation's own configuration. It tells Cursor how to work on foundation itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything foundation configures →

not rated 2repo 2mo ago A scan 25 tokens copy · 95% MIT
View source ↗ markmhendrickson/foundation
Reuse

Borrowing it

Nothing to install: this file belongs to markmhendrickson/foundation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/markmhendrickson/foundation/main/.cursor/skills/create-plan/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Cursor.

Wrote 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.

agentmods badge for create-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-plan/github.svg)](https://agentmods.dev/skills/markmhendrickson/foundation/create-plan)
Your own site
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/create-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-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.

agentmods 80×15 button for create-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/markmhendrickson/foundation/create-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/foundation/create-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 686 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00686
Opus 5.5 $0.00010 $0.00274
Sonnet 5.5 $0.00005 $0.00137
Haiku 4.5 $0.00003 $0.00069

Measured 1mo ago against content hash 78ed4c74bcf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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.

Origin

This is a copy

95% identical to create-plan — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/skills/create-plan/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create New Plan

Create a new plan entity in Neotoma with title = {{input:title}}.

Follow the complete workflow in foundation/development/plan_workflow.md. Configuration is read from foundation-config.yaml.

This workflow can also be triggered automatically via .cursor/rules/plan_detection.mdc when you mention planning-related patterns in natural language (e.g., "create plan", "new plan"). Both paths execute the same workflow.

Workflow Overview

Implements Checkpoint 0 of the plan creation workflow:

  1. Collect required plan fields from the user
  2. Run alignment check (summary → user confirms)
  3. Store plan as a Neotoma plan entity
  4. Create relationships to related entities
  5. Optionally rebuild the neotoma-plans mirror

Tasks

  1. Collect required fields:

    Ask the user for any missing required fields:

    • title — Short, imperative name
    • description — Problem being solved and why it matters
    • scope — What is explicitly in scope
    • out_of_scope — What is explicitly out of scope
    • success_criteria — Measurable conditions for completion
    • status — Default to draft

    Optional fields to offer (collect if relevant):

    • priority (P0/P1/P2/P3)
    • phase
    • target_release
    • deliverables
    • dependencies (canonical names of plans this plan requires)
    • testing_notes
    • observability_notes

  2. Alignment check:

    After collecting fields, produce a concise summary:

    • Problem it solves and why it exists
    • What is explicitly in scope and out of scope
    • Critical constraints or invariants

    Ask: "Does this accurately capture what you want this plan to do?"

    Incorporate corrections and re-summarize if changes are substantial. Do not proceed until the user confirms.

  3. Store the plan:

    Use store or submit_entity with:

    • entity_type: plan
    • All collected fields as snapshot fields

  4. Create relationships (if relevant entities are mentioned or known):

    • REFERS_TO for objectives, releases, or parent plans
    • DEPENDS_ON for plans this plan requires
    • INFORMED_BY for issues, feedback, or research

Read the full file on GitHub · 93 lines

Changes

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.

  1. 1mo ago First seen · 93 lines · 25 tokens per session scan A 78ed4c74bcf4

Subscribe to this mod's changes

create-plan is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 686 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to create-plan, differing in 9 lines, and is treated as a copy.

PlanningProject management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens