Borrowing it
Nothing to install: this file belongs to agentculture/learn-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentculture/learn-cli/main/.claude/skills/summarize-delivery/SKILL.mdgit clone --depth 1 https://github.com/agentculture/learn-cliWrote 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/agentculture/learn-cli/summarize-delivery)<a href="https://agentmods.dev/skills/agentculture/learn-cli/summarize-delivery"><img src="https://agentmods.dev/badge/skills/agentculture/learn-cli/summarize-delivery/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/agentculture/learn-cli/summarize-delivery"><img src="https://agentmods.dev/badge/skills/agentculture/learn-cli/summarize-delivery.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.00199 | $0.05351 |
| Opus 5.5 | $0.00080 | $0.02140 |
| Sonnet 5.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 2mo 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.
- 2mo 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 3mo ago), licensed Apache-2.0. It adds 199 tokens to every session and 5,351 once invoked, about $0.0008 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.