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/generate-extensionnpx skills add DailybotHQ/deepworkplan-skill --skill generate-extensiongit 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/generate-extension)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/generate-extension"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/generate-extension.svg" alt="Measured on agentmods" 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 | $0.00167 | $0.03570 |
| Opus 5 | $0.00084 | $0.01785 |
| Sonnet 5 | $0.00033 | $0.00714 |
| Haiku 4.5 | $0.00017 | $0.00357 |
Grade A, and why
ai-diff-reviewer-generate-extension scanned grade A with 1 finding 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 5d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `subprocess`, `os.system`, `child_process`, shell exec, `eval`, `exec`. How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Diff Reviewer — Generate Extension (sub-skill)
Companion to the ai-diff-reviewer skill. Where
ai-diff-reviewer runs the review, this sub-skill bootstraps the
configuration — turning "here's the default reviewer" into "here's a
reviewer that understands OUR stack, OUR conventions, and OUR history of
bugs."
Two output modes:
| Mode | File written | When |
|---|---|---|
| Extension (default) | .review/extension.md |
Almost always — the recommended path. Layers repo-specific overrides ON TOP of the battle-tested default prompt. Cheap iteration; the default keeps improving upstream. |
| Full replacement (advanced) | .github/prompts/pr-review.md |
Rare — teams that want total control, or whose codebase is so idiosyncratic (proprietary DSL, unusual paradigm) that the default is more noise than signal. Requires ongoing maintenance; you lose upstream improvements to the default. |
Activation
- "Generate a
.review/extension.mdfor this repo" - "Customize the code review for our project"
- "Help me write repo-specific review rules"
- "Set up the AI reviewer for this codebase"
- "Tailor the reviewer to our stack"
- "Bootstrap the extension file"
The parent ai-diff-reviewer skill also routes to this
sub-skill in two situations:
- Explicit intent — the developer asks for setup/customization instead of running a review (any of the triggers above).
- Automatic bootstrap — the developer runs the review on a repo
with no
.review/extension.mdand no.review/.skip-bootstrapmarker, and answers yes at the Step 2.5 prompt in the parent skill. In this case, when this sub-skill finishes writing the file, control returns to the parent skill's Step 2 which layers the fresh extension onto the base prompt and continues the review.
Both entry paths run the same Discovery + Write flow below. Do not skip Discovery just because the invocation came from the bootstrap offer — the whole value of the extension is the file-anchored Discovery evidence, not the file itself.
What ships with it
1 file 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.
- 5d ago First seen · 350 lines · 167 tokens per session scan A fa0d970a139e
ai-diff-reviewer-generate-extension is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 167 tokens to every session and 3,570 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…