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/authornpx skills add DailybotHQ/deepworkplan-skill --skill authorgit 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.00081 | $0.01935 |
| Opus 5 | $0.00041 | $0.00967 |
| Sonnet 5 | $0.00016 | $0.00387 |
| Haiku 4.5 | $0.00008 | $0.00194 |
Grade A, and why
deepworkplan-author 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Author
Author and maintain the current repository's agent kit: reusable skills, agents, and commands. Reason about the repo — never copy a generic kit. This sub-skill is also the executor of the mandatory "Skills & Agents Discovery" plan task.
Concepts
- Skill — a reusable, parameterized procedure invoked in-session (e.g.
/fix-lint). Encodes "how to do X". Lives in<skills-dir>/<name>/SKILL.md. - Agent — a specialized worker definition (role, model tier, tools, system prompt) dispatched to
handle a class of tasks (e.g.
reviewer,executor). Encodes "who does X". Lives in<agents-dir>/<name>.md. - Command — a thin slash-command entry point that routes to a skill or agent. Logic stays in the skill/agent; the command is a delegator.
| Need | Create |
|---|---|
| A repeatable procedure run in-session | Skill |
| A persistent role with its own model tier / tools | Agent |
| A shortcut to invoke a skill or agent | Command |
Step 0 — Detect the repo layout (do NOT assume)
Before authoring anything, discover where this repo keeps its kit. Do not hardcode any single repo's conventions.
- Find the agent root: look for
.agents/, then.claude/or.cursor/(often symlinks to.agents/), then anyAGENTS.md/CLAUDE.mdat the repo root for documented paths. - Within it, locate
skills/,agents/,commands/, and a catalog underdocs/. - Inspect 1-2 existing skills/agents to learn the repo's local conventions (frontmatter keys it uses, naming, body structure, whether commands are thin delegators). Match them.
ls -d .agents .claude 2>/dev/null
ls .agents/skills .agents/agents .agents/commands .agents/docs 2>/dev/null
ls AGENTS.md CLAUDE.md 2>/dev/null
If the repo has no .agents/ layout yet, route the developer to the onboard sub-skill first
(onboard/SKILL.md) — onboarding scaffolds the directories this sub-skill writes into.
Flows
What ships with it
2 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 · 178 lines · 81 tokens per session scan A d936953faf27
deepworkplan-author is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,935 once invoked, about $0.0004 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.