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/devcontainernpx skills add DailybotHQ/deepworkplan-skill --skill devcontainergit 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.00103 | $0.01380 |
| Opus 5 | $0.00051 | $0.00690 |
| Sonnet 5 | $0.00021 | $0.00276 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
deepworkplan-addon-devcontainer 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Devcontainer Addon
Add a reproducible, isolated dev container to the target repo so any human or AI agent gets the same environment, with AI-CLI auth that survives rebuilds. This is the methodology's first opt-in addon — it is never required for a repo to be AI-first.
The rule that overrides everything: REASON about the repo, then generate
~85% of every Dailybot devcontainer is identical — that common skeleton is the stable part you carry forward. ~15% is repo-specific — base image, user,
workspaceFolder, supporting services, ports, secrets — and that part you reason out from the target repo's actual stack, never by copying one reference repo. The one near-verbatim exception is the AI-CLI persistence entrypoint (templates/entrypoint.md): it is stable enough to copy with only the home-path / user adjusted.
Read these first (all relative inside the skill)
SPEC.md— the normative (RFC-2119) contract: common skeleton, per-repo reasoning checklist, project-identity precedence, validation rule, public-OSS variant.templates/presets.md— the 7 reasoning presets (node-web, node-service, node-lambda, python-service, python-cli-oss, static-site, orchestrator-hub). Match one as a starting checklist, then verify every assumption against the real repo — detected reality wins.- The other
templates/*.md— reasoning guides for each file you generate. ../README.md— the addon mechanism (opt-in, reconcile-don't-clobber, contract).
When this runs
- From
onboardPhase 7b — after the core AI-first scaffolding,onboardoffers this addon; if accepted it reads this SKILL and runs the flow below. - Directly —
/deepworkplan-addon-devcontaineron an already-onboarded repo to add or reconcile a devcontainer.
The flow
Step 0 — Consent + reconcile check
- Confirm the developer wants a devcontainer (skip silently if declined — the repo stays baseline-conformant).
- Detect existing setup. Look for
.devcontainer/,docker/,docker-compose.{yml,yaml}, aDockerfile. If any exist, you are in reconcile mode: you MUST preserve working values and MUST NOT overwrite or delete files without explicit approval (see SPEC §Reconcile).
What ships with it
7 files 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 · 101 lines · 103 tokens per session scan A 0fa698ccd1e7
deepworkplan-addon-devcontainer is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 103 tokens to every session and 1,380 once invoked, about $0.0005 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…