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.
git 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/commands/dailybothq/deepworkplan-skill/commit)<a href="https://agentmods.dev/commands/dailybothq/deepworkplan-skill/commit"><img src="https://agentmods.dev/badge/commands/dailybothq/deepworkplan-skill/commit/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/commands/dailybothq/deepworkplan-skill/commit"><img src="https://agentmods.dev/badge/commands/dailybothq/deepworkplan-skill/commit.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.00015 | $0.00379 |
| Opus 5.5 | $0.00006 | $0.00152 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
commit 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 1mo 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.
What it actually says
/commit
Create a commit whose message drives this repo's automatic versioning. The
auto-release.yml workflow reads merged commit messages to pick the bump level,
so the <type>(<scope>): prefix is not cosmetic — it is the release input.
What to do
-
Run the local gate first (
/run-tests) and confirm it is clean. -
Stage the intended changes (review
git status/git difffirst — never blind-stage). Respect the ship boundary: runtime files only underskills/deepworkplan/, dev-infra at the repo root /.agents//.github/. -
Write the message in this format:
<type>(<scope>): <short description> <body — what changed, why, risks> Co-Authored-By: <agent name + version> <[email protected]>- Types:
feat,fix,docs,chore,test,ci,refactor - Scopes:
skill,create,execute,refine,resume,status,onboard,addon,shared,setup,ci,docs,release - Bump mapping (the bot reads this):
feat(...)!:/BREAKING CHANGE:→ MAJOR ·feat(...):→ MINOR · everything else → PATCH
- Types:
-
Do NOT hand-edit
version:fields orCHANGELOG.md— the bot owns them. -
Commit only when the user asks. If on
main, branch first.
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.
- 1mo ago First seen · 35 lines · 15 tokens per session scan A e2a7d6969c39
commit is a command published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 379 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 commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…
approve-proposed
Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…
pr-package
Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…
util.git-commit-message
Generate conventional commit message and description from the current changes diff.
standup
Review my git commits from the past workday and generate a standup summary.