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/dailybothq/deepworkplan-skill/refinenpx skills add DailybotHQ/deepworkplan-skill --skill refinegit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillWhat 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.00053 | $0.01594 |
| Opus 5 | $0.00026 | $0.00797 |
| Sonnet 5 | $0.00011 | $0.00319 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
deepworkplan-refine 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Refine
Polish a refined draft or modify an existing final plan (add / edit / reorder tasks, update the README).
Single-step change (vs legacy): there is exactly one draft artifact — the refined draft at
.dwp/drafts/PLAN_{name}_draft_refined.md. Refining a draft edits it in place (or converts it into a final plan). The legacy distinction where "refine the draft" produced a separate_refinedfile from a raw draft is gone, and the old three-option "Refine / Convert / Both" collapses to Edit in place or Convert to plan.
Shared resources (read these)
../shared/dwp-paths.md— drafts at.dwp/drafts/, plans at.dwp/plans/PLAN_{name}/.../shared/context.sh— resolvedwp_dir.../guide/GUIDE.md— plan/task structure and mandatory final tasks.../examples/CREATE_PLAN.md— prompt patterns for professional rewriting.
Parameter Support
| Parameter | Description | Example |
|---|---|---|
| (none) | Interactive — choose draft or plan | /dwp-refine |
{draft_filename} |
Refine a specific refined draft | /dwp-refine PLAN_x_draft_refined.md |
latest |
Refine the most recent refined draft | /dwp-refine latest |
plan {plan_name} |
Modify an existing final plan | /dwp-refine plan auth_refactor |
plan latest |
Modify the most recent plan | /dwp-refine plan latest |
Workflow
Step 0 — Determine Target Type
- No parameters → Step 1 (interactive).
- A draft filename /
latest→ Step 2 (Draft Workflow). plan {name}/plan latest→ Step 3 (Plan Workflow).
Step 1 — Interactive Selection
Ask whether to refine a draft (polish or convert to a final plan) or an existing final plan (add tasks, modify instructions, adjust context). Route to Step 2 or Step 3.
Draft Workflow
Step 2 — Select and Refine the Refined Draft
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.
- 2d ago First seen · 133 lines · 53 tokens per session scan A d11fb0022635
deepworkplan-refine is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,594 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.