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 skills add DailybotHQ/deepworkplan-skill --skill address-reviewgit 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/address-review)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/address-review"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/address-review/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/skills/dailybothq/deepworkplan-skill/address-review"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/address-review.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.00225 | $0.06567 |
| Opus 5.5 | $0.00090 | $0.02627 |
| Sonnet 5.5 | $0.00045 | $0.01313 |
| Haiku 4.5 | $0.00022 | $0.00657 |
Grade A, and why
ai-diff-reviewer-address-review 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 3d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Diff Reviewer — Address Review (sub-skill)
The one-invocation loop for the most repeated instruction after a CI round: "revisa los comentarios del reviewer en el PR, resuélvelos y luego haz toggle del ready label." The reviewer's comments are only half of a PR's health, so the loop is green-CI aware: every OTHER workflow the PR runs — the codecheck that runs tests, linters and typecheck; build jobs; the branch-protection rule that requires the branch to be up to date with its base — is surveyed too, and a red one is diagnosed from its logs and fixed in the same consented pass, before the reviewer is re-armed. This sub-skill is that whole sentence, executable — and repo-adaptive: it discovers how THIS repository triggers its reviewer (label gate or push trigger) and re-arms it the right way instead of guessing.
Relationship to the family:
apply-reviewreads a CI review and walks findings with a no-commit / no-push boundary (each apply is a working-tree edit needing a per-finding yes).- This sub-skill closes the loop: same finding-loading rules (v3 review-output artifact first, marker comment + live threads as fallback, minimized and stale reviews skipped), but the apply step ends in commits and a push (small Conventional Commits batches), the push/label step re-arms the CI reviewer, and the CI-health sweep (Step 2) fixes whatever else is red on the PR so the next round starts on a green repo.
- On a repo with no reviewer workflow, it says so and offers the parent skill's local review flow instead of pretending a round will start.
When it fires
- "Address the review and re-run"
- "Resolve the reviewer comments and toggle ready"
- "Fix the review findings and re-trigger CI"
- "Fix the failing workflows" / "make CI green and re-run the reviewer"
- "The PR is red — loop the review"
- "Loop the review" / "run the review loop"
- "The PR has no review yet — trigger it" / "start the first review round"
- The repeated instruction itself: "revisa los comentarios del reviewer, resuélvelos y haz toggle del ready label"
- "What's left from the review? Handle it and re-arm CI"
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.
- 3d ago Changed 7443b396b01c
- 4d ago Changed f494b59082a3
- 5d ago Changed 454938027b85
- 7d ago Changed 89cec2e05ab3
- 10d ago Changed 9ad0cd44baa8
- 18d ago Changed · +231 lines · +19 tokens per session 2ab30ebae64a
- 21d ago First seen · 185 lines · 206 tokens per session scan A 87d0e2ed9cc8
ai-diff-reviewer-address-review is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 225 tokens to every session and 6,567 once invoked, about $0.0009 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-09-26.
Other skills, from other repositories
gsd-pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
extract-pr-review-rules
Extract a repository's inline PR review comments into a per-reviewer pr-review-rules doc for the project's review skills, resuming from the last run's checkpoint.
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.