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/run-tests)<a href="https://agentmods.dev/commands/dailybothq/deepworkplan-skill/run-tests"><img src="https://agentmods.dev/badge/commands/dailybothq/deepworkplan-skill/run-tests/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/run-tests"><img src="https://agentmods.dev/badge/commands/dailybothq/deepworkplan-skill/run-tests.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.00020 | $0.00277 |
| Opus 5.5 | $0.00008 | $0.00111 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
run-tests 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
/run-tests
Reproduce locally what .github/workflows/ci.yml runs on every PR, in order.
Stop at the first failure and fix before moving on.
What to do
-
Frontmatter —
python3 scripts/validate-frontmatter.py -
Shell lint —
shellcheck setup.sh skills/deepworkplan/shared/context.sh scripts/*.sh -
Unit tests (bats-core) —
bats tests/(coverscontext-sh.bats,setup-sh.bats) -
Installer smoke test against a throwaway HOME (never touches
~/.claude):HOME="$(mktemp -d)" ./setup.sh --host claude -
context.sh smoke —
bash skills/deepworkplan/shared/context.sh(must emit single-line JSON)
All shell scripts must run on bash 3.2 (macOS default): no mapfile,
no declare -A, no ${var^^}. CI runs the smoke job on both ubuntu-latest
and macos-latest to enforce this — keep new shell code 3.2-safe.
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 · 26 lines · 20 tokens per session scan A e19d77b8e684
run-tests is a command published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 277 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
spec-impl
Execute spec tasks using TDD methodology.
kiro-validate-impl
Command "kiro-validate-impl" from gotalab/cc-sdd, covering implementation validation, core task, execution steps, 1. detect validation target and 2. load context.
speckit.companion.living-validate
Check the shape of living specs and a feature spec's deltas — a requirement with no scenario, a scenario missing WHEN or THEN, a duplicate heading, a delta pointing at nothing (opt-in, read-only, never halts).
speckit.companion.living-coverage
Report living-spec requirement→test coverage — per requirement, whether its coverage tier maps a test (opt-in, read-only, never halts).
build
Plan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.