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/statusnpx skills add DailybotHQ/deepworkplan-skill --skill statusgit 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.00038 | $0.00843 |
| Opus 5 | $0.00019 | $0.00421 |
| Sonnet 5 | $0.00008 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
deepworkplan-status 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Status
Report the current state of one or more Deep Work Plans — progress, completed tasks, current task, blockers — without executing or modifying anything.
Shared resources (read these)
../shared/context.sh— resolvedwp_dir.../shared/dwp-paths.md— plans at.dwp/plans/PLAN_{name}/.
Parameter Support
/dwp-status {plan_name}— check a specific plan./dwp-status latest— check the most recently modified plan./dwp-status all— check all plans.- No parameter → interactive scope selection (Step 1).
Normalize the PLAN_ prefix; validate that single plans exist under
.dwp/plans/. If not found, show available plans and ask the user to choose.
Workflow
Step 0 — Check for Parameters
all → scope "all", skip to Step 2. latest → most recent plan, scope "single",
skip to Step 2. Otherwise normalize the name, validate, scope "single", skip to
Step 2. No parameter → Step 1.
Step 1 — Ask for Scope
List PLAN_* folders in .dwp/plans/; mark the most recently modified as
latest. Offer: a single plan (from a numbered list), all plans, or latest.
Accept a number, name, all, or latest.
Step 2 — Gather Status Information
For each plan: read the README (goal, task list [x]/[ ], plan-status notes);
run git status and git log --oneline -20; read the last completed task's
Completion & Log and the current [ ] task file; compute totals and progress %.
Step 3 — Generate Status Report
Single plan: header with Plan Status: PLAN_{name} and location
.dwp/plans/PLAN_{name}/; goal; progress (total / completed / pending / %);
completed tasks; pending tasks; current status (last completed, next task,
uncommitted work, recent commits); notes from the README; last task log summary.
All plans: a one-line-per-plan summary (progress, status, last activity), then the single-plan detail block for each.
Step 4 — Additional Information (optional)
Offer deeper detail for any plan: all task files and status, git diff for
uncommitted changes, full last-task completion log, any blockers.
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 · 80 lines · 38 tokens per session scan A 45e5e30e0484
deepworkplan-status is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 843 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-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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…