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/setupnpx skills add DailybotHQ/deepworkplan-skill --skill setupgit 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.00180 | $0.04681 |
| Opus 5 | $0.00090 | $0.02341 |
| Sonnet 5 | $0.00036 | $0.00936 |
| Haiku 4.5 | $0.00018 | $0.00468 |
Grade A, and why
ai-diff-reviewer-setup 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Diff Reviewer — Setup Wizard (sub-skill)
Companion to the ai-diff-reviewer skill. Where the parent
runs the review and generate-extension
tailors the prompt, this sub-skill bootstraps the GitHub Action
itself — walks the developer through the ~6 key decisions and writes
a working .github/workflows/pr-review.yml tailored to those choices.
Also doubles as the reference manual for every action.yml input:
if a developer asks any coding agent "what does strictness do?" or
"how do I run only when a label is added?", the agent can read
reference.md in this directory and answer without
opening the source.
When it fires
Explicit triggers (recommended):
- "Set up AI Diff Reviewer for this repo"
- "Configure the reviewer action"
- "Install the AI Diff Reviewer GitHub Action"
- "Help me create the pr-review workflow"
- "How do I add AI Diff Reviewer to this project?"
The parent ai-diff-reviewer skill may also route here
automatically when a review-flow request activates on a repo that
clearly has no .github/workflows/pr-review.yml (opt-in — future
enhancement; not the default today).
Step 0 — Trust boundary
This skill writes exactly two categories of files, both with explicit developer consent:
.github/workflows/pr-review.yml— the tailored workflow after all six questions are answered. If a file already exists at that path, the skill ASKS before overwriting (offers to write topr-review-new.ymlalongside for review)..review/extension.md— only if the developer says yes to the optional Step 5 handoff, which invokes thegenerate-extensionsub-skill.
It does not:
- Commit anything, push anything, or open a PR — the developer stages and commits themselves.
- Touch GitHub Secrets — they're set once by the developer in the repo's Settings UI (link surfaced in Step 4).
- Modify existing unrelated workflows in
.github/workflows/. - Call the LLM provider directly or send data off the machine.
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.
- 2d ago First seen · 464 lines · 180 tokens per session scan A 584ae1b650f8
ai-diff-reviewer-setup is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 180 tokens to every session and 4,681 once invoked, about $0.0009 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.
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…
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…