Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hlalljie/agent-workflow-presets/main/.cursor/skills/draft-plan/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/skills/hlalljie/agent-workflow-presets/draft-plan)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/draft-plan"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/draft-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/skills/hlalljie/agent-workflow-presets/draft-plan"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/draft-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.00031 | $0.00928 |
| Opus 5.5 | $0.00012 | $0.00371 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
draft-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 19d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft plan
When to use
Only when the user explicitly asks to create a plan or invokes this skill. Do not auto-launch into planning. If you think something needs a plan but the user hasn't asked, you can suggest "Would you like to create a plan for this?" but only for large multi-phase efforts.
What a plan produces
A plan file, and potentially open questions and research docs. Never code, never create tasks. Task lists are a separate skill (create task list) invoked later when the user is ready to work on a phase.
File locations (always use these):
- Plan:
.cursor/plans/<plan-name>/plan.md - Research docs:
.cursor/plans/<plan-name>/research/<topic>.md - Open questions:
.cursor/plans/<plan-name>/open-questions.md - Decisions:
.cursor/plans/<plan-name>/decisions.md - Phase task lists:
.cursor/plans/<plan-name>/<phase>/tasks/tasks.md - Finished plans move whole to
.cursor/plans-archive/<plan-name>/(archive-plan).
Process
- Read relevant context: codebase, conversation history, existing research, existing open questions. Also read
docs/decisions.mdanddocs/architecture.mdif they exist, and check.cursor/plans-archive/for finished plans in the same area. - If the codebase can answer a question, explore it instead of asking the user.
- Ask questions to resolve unknowns — one or two at a time, not a wall of questions. Work through the decision tree branch by branch. For each question, provide your recommended answer.
- Create open questions for anything that needs research or will block work later.
- For questions that need research, spawn a subagent following research skill.
- Write the plan only after enough questions are answered to define phases.
- Present to user for review.
Plan format
Each phase is self-contained. A reader looking at one phase should find everything relevant to that phase without scrolling elsewhere. Research, open questions, and details are linked or listed under the phase they belong to, not in separate sections at the bottom.
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.
- 19d ago Changed · +2 lines 47619a1e0546
- 22d ago Changed aebed6a677cf
- 1mo ago First seen · 82 lines · 31 tokens per session scan A 7c9ccb51a436
draft-plan is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 31 tokens to every session and 928 once invoked, about $0.0001 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 skills, from other repositories
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
update-installed-skills
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.