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 skills/hlalljie/agent-workflow-presets/draft-plannpx skills add hlalljie/agent-workflow-presets --skill draft-plangit 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.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.1 | $0.00031 | $0.00814 |
| Opus 5 | $0.00015 | $0.00407 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
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 5d 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 — 82 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
Process
- Read relevant context: codebase, conversation history, existing research, existing open questions.
- 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 using
[MODEL:researcher]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.
# Plan: <name>
## Overview
2-3 sentences on what and why.
## Phase 1: <name>
Short description of what this phase delivers.
- Detail or decision relevant to this phase
- Detail with link to [research](research/some-doc.md) if needed
- Blocked by open question 3
## Phase 2: <name>
Short description.
- Detail
- Detail
## Backlog
Phases that are known but not ready to be worked on yet. Same format as active phases but may have less detail.
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.
- 5d 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 1mo ago), licensed MIT. It adds 31 tokens to every session and 814 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 skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.