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/agentculture/learn-cli/summarize-deliverynpx skills add agentculture/learn-cli --skill summarize-deliverygit clone --depth 1 https://github.com/agentculture/learn-cliWhat 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.00199 | $0.05351 |
| Opus 5 | $0.00100 | $0.02676 |
| Sonnet 5 | $0.00040 | $0.01070 |
| Haiku 4.5 | $0.00020 | $0.00535 |
Grade A, and why
summarize-delivery 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.
This is a copy
100% identical to summarize-delivery — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
summarize-delivery — turn a workforce run into an accountability artifact
The skill is named summarize-delivery; it is the delivery-side closure
leg that closes the devague method's six-leg flow:
scope -> think -> spec-to-plan -> assign-to-workforce -> deviate -> summarize-delivery
It runs after the sibling /assign-to-workforce skill has executed (or
attempted to execute) a converged plan — and after any /deviate records
that run produced, since /deviate slots in between
/assign-to-workforce and this skill, recording approved mid-run departures
the moment they happen during the fan-out. Where /assign-to-workforce takes
the plan to delivery, this skill summarizes that delivery: it separates
what was planned from what was actually delivered, records the
mid-work decisions and plan drift the execution produced — quoting
/deviate's approved dN records as the recorded ground truth wherever they
cover an item — states delivery claims with evidence and confidence, and
names the remaining work.
The plan the user confirmed is a contract, not a fiction. Agents make mid-work decisions, hit constraints, cut scope, and produce delivery claims that were never in the plan. Until now the flow had no wrap-up leg to record any of it. This skill is that leg: the summary records where execution obeyed the contract, where it changed, and what is actually safe to claim as delivered.
It is not a polite progress report and not a restatement of the plan. It is an accountability artifact — auditable by a human who never watched the run.
The three readers
Write for exactly these three, and no one who was present for the execution:
- The operator (main agent) closing a workforce run — assembling the ground truth of what merged, what failed, and what still needs doing.
- The human owner at the final PR gate — who uses the artifact as the review map: every delivery claim traces to a plan task or an explicit drift entry, so the plan-versus-actual comparison is mechanical, not rhetorical.
- Any later reader who needs to know what actually shipped without replaying the execution transcript. The artifact is committed and self-contained; nothing in it depends on unrecorded memory of the run.
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 · 441 lines · 199 tokens per session scan A 9c9254234d86
summarize-delivery is a skill published in the GitHub repository agentculture/learn-cli (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 199 tokens to every session and 5,351 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to summarize-delivery, differing in 0 lines, and is treated as a copy.
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…