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 skills add DailybotHQ/deepworkplan-skill --skill statusgit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillWrote 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/dailybothq/deepworkplan-skill/status)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/status"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/status/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/dailybothq/deepworkplan-skill/status"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/status.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.00034 | $0.02244 |
| Opus 5.5 | $0.00014 | $0.00898 |
| Sonnet 5.5 | $0.00007 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00224 |
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 3d 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 — 172 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, checkpoint, blockers, consistency — without executing or modifying anything, and without loading the whole plan.
Shared resources (read these)
../shared/context.sh— resolvedwp_dir.../shared/dwp-paths.md— plans at.dwp/plans/<plan>/.- Guide (essential — read for this flow): none. Status is a read-only report; it does not load the methodology guide.
Parameter Support
/dwp-status {plan_name}— check a specific plan./dwp-status latest— check the highest numbered plan, or the most recently modified legacy 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.
Lite-aware status
For v2 plans report format, materialization, approval and promotion separately
from execution progress. Read them from state.json; fall back to the README's
Approval row when the field is absent, and to pending when neither is present. A ready pending-review Lite proposal is valid but not
executable. Resolve inline task locators against unique README anchors and count
only canonical task-index checkboxes, never fenced examples. Report a missing or
duplicate anchor, pending approval, or promotion marker as a finding; do not
repair it in this read-only flow.
Trust boundary (write scope)
This skill is read-only by contract. allowed-tools lists Bash (which
Trust Hub treats as write-capable in general) — here it is used exclusively
for read-only inspection. Status reads plan folders, progress checkmarks, and
state.json, and reports; it performs no writes of any kind.
It MUST NOT: modify tasks, progress, state.json or source files; "fix" a
plan while reporting on it; or write anywhere. If the status reveals an
inconsistency, report it and point at refine/resume — do not repair it
silently.
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.
- 3d ago Changed 1ac10512e214
- 4d ago Changed 9bc5b643f9f1
- 5d ago Changed ce11c740dc41
- 6d ago Changed f0782b6f8b83
- 7d ago Changed · +12 lines dc2bc8a8d66a
- 9d ago Changed 30b712056c75
- 11d ago Changed bfe0e918e297
- 15d ago Changed e7ffd7b43b16
- 18d ago Changed · +25 lines e92fb77524b1
- 29d ago First seen · 135 lines · 34 tokens per session scan A 8d4a09de533c
deepworkplan-status is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 2,244 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-30.
Other skills, from other repositories
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…
review
Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.