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/blakemartz/delivery-loop/patch-tasknpx skills add blakemartz/delivery-loop --skill patch-taskgit clone --depth 1 https://github.com/blakemartz/delivery-loopWhat 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.00054 | $0.00921 |
| Opus 5 | $0.00027 | $0.00461 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
patch-task 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 yesterday.
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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
patch-task — fix a PR that got changes-requested
You are the patcher role from the delivery spec (${CLAUDE_PLUGIN_ROOT}/docs/agentic_delivery_spec.md, §3.5, §9). Read .claude/delivery.conf for GATE_CMD, BASE_BRANCH, and NOTIFY_ESCALATE_CMD.
Protocol
- Check the iteration budget.
gh pr view <pr> --json comments— find the latestPatch iteration: n/3comment. If n is already 3: add labelneeds-humanto the PR and linked issue, comment a summary of the impasse, runNOTIFY_ESCALATE_CMDif set, and STOP. Do not patch. - Gather findings. The review:
gh pr view <pr> --json reviews,comments(request-changes body + line comments). CI:gh pr checks <pr>— read the failing run logs viagh run view <run-id> --log-failedif red. - Re-enter the task worktree.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/task-worktree.sh" <issue#>returns the existing worktree (it re-creates it from the branch if it was cleaned up). Work only there. - Fix every finding. Address each review point and each failing check — and fix it toward the best-practice, idiomatic solution (spec §2.1), not just enough to silence the finding. If you disagree with a finding, don't silently ignore it — reply to the review comment with your reasoning and make the call visible.
- Rebase onto
origin/$BASE_BRANCHif behind. Resolve conflicts here in the worktree. Never force-push over review history (after a rebase,--force-with-leaseis acceptable only if the rebase itself required it; prefer plain pushes of fixup commits). - Re-verify. Every acceptance criterion from the linked issue + the gate (
GATE_CMD). Hooks fire on commit/push; never bypass the gate. - Push, then: comment
Patch iteration: <n+1>/3plus a short change summary on the PR; flip the issue back:gh issue edit <N> --add-label status:in-review --remove-label status:changes-requested. - Report what changed and that the PR awaits re-review.
Encode the lesson: if the finding traces back to a harness gap (a criterion the gate should have caught, an ambiguous template), file a module:infra task.
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.
- yesterday First seen · 34 lines · 54 tokens per session scan A 628d912c5887
patch-task is a skill published in the GitHub repository blakemartz/delivery-loop (4 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 921 once invoked, about $0.0003 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-31.
Other skills, from other repositories
zh-output-example
Reviews Chinese skill documentation for publication readiness. Invoke when the user asks in Chinese to review a skill.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
powerpoint
Create designed, editable PowerPoint .pptx presentations with PptxGenJS. Use when the user asks to create, generate, update, or inspect a deck, slide deck, presentation, or .pptx file.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.