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/verifynpx skills add DailybotHQ/deepworkplan-skill --skill verifygit 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.00059 | $0.02137 |
| Opus 5 | $0.00030 | $0.01069 |
| Sonnet 5 | $0.00012 | $0.00427 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
deepworkplan-verify 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Verify (conformance check)
Check, objectively, whether a repository is DeepWorkPlan-conformant (AI-first and agent-pilotable) and whether its Deep Work Plans are well-formed. This sub-skill is read-only: it reports pass/fail, it does not change files. The normative criteria are defined in the specification's Conformance document (https://deepworkplan.com/spec).
Shared resources (read these)
../shared/context.sh— resolve the repo root and.dwp/.../shared/dwp-paths.md— plans live at.dwp/plans/PLAN_{name}/.conformance.sh— the mechanical conformance layer (run it first).../spec/PLAN_STATE.md— the machine-readable state layer the desync checks enforce.
Run the mechanical layer first
Start every verification by running the automated checker — it covers the
structural checks below objectively, exits 0/1, and detects
markdown-vs-state.json desync:
bash {skill_dir}/verify/conformance.sh # repo + every plan
bash {skill_dir}/verify/conformance.sh --repo-only
bash {skill_dir}/verify/conformance.sh --plan PLAN_{name}
Its exit code is CI-friendly: a repo can run it as a pipeline gate. Then layer the judgment checks (real commands, real toolchain, catalog-matches-disk) on top — the script verifies structure; you verify substance.
Parameter support
/dwp-verify— verify the repository (the default)./dwp-verify plan {name}— also verify a specific plan's well-formedness./dwp-verify all— verify the repository and every plan under.dwp/plans/.
The overriding rule
Report what is true on disk, not what should be true. A criterion passes only if the artifact exists and carries real, repository-specific content. A generic stub, a placeholder, or a command that cannot run in this repository fails the criterion — say so explicitly. Never mark a check passed without evidence.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 145 lines · 59 tokens per session scan A 5ecba05daa7a
deepworkplan-verify is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,137 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.
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…