A close-out workflow inventories a managed agent, regenerates a shareable overview page, and suggests the next one or two upgrades. It records which parts of the agent setup and workflow are complete.

It is for summarizing an agent's environment, memory, outcome checks, deployment, completed phases, and suggested improvements.

It prevents the final state, ownership details, and follow-up work from being lost after an agent is launched.

wrap-up — Skill for Claude Code by alirezarezvani/claude-skills

About the project

claude-skills is a large collection of reusable skills, commands, plugins, and supporting resources for coding agents across engineering, business, research, compliance, and productivity work. It is used by people who want agents such as Claude Code, Codex, Gemini CLI, or Cursor to follow specialized workflows. The catalogue contains selected skills and settings from the collection.

alirezarezvani/claude-skills · 28,607 stars · on GitHub · alirezarezvani.medium.com

Install

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.

Any agent

npx skills add alirezarezvani/claude-skills --skill wrap-up

Clone the repo

git clone --depth 1 https://github.com/alirezarezvani/claude-skills

Made for: Claude Code.

Or install agent-launcher-skills, the plugin that ships this one along with the rest of its 6 skills, 8 commands, 4 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/wrap-up/github.svg)](https://agentmods.dev/skills/alirezarezvani/claude-skills/wrap-up)

Your own site

<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/wrap-up"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/wrap-up/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alirezarezvani/claude-skills/wrap-up"><img src="https://agentmods.dev/badge/skills/alirezarezvani/claude-skills/wrap-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 150 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 765 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00150	$0.00765
Opus 5.5	$0.00060	$0.00306
Sonnet 5.5	$0.00030	$0.00153
Haiku 4.5	$0.00015	$0.00076

Measured today against content hash 77089d2d96ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wrap-up 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 today.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/overview_page.py, scripts/primitives_inventory.py, scripts/upgrade_suggester.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

agent-launcher/skills/wrap-up/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wrap-up — close it out

The explicit close-out. Confirm what's live, regenerate the shareable overview, and name the next 1–2 upgrades so the founder leaves with a clear roadmap. The ./my-agent/ folder keeps working after the session ends.

Workflow

Inventory what they own.
```
python3 scripts/primitives_inventory.py \
  --sheet ./my-agent/build-sheet.json --goal ./my-agent/goal.json
```
Tables agent / environment / session / memory / outcome / deployment and the phases completed.

Regenerate the overview page.

python3 scripts/overview_page.py \
  --sheet ./my-agent/build-sheet.json --out-dir ./my-agent \
  --status live --loop-shape cron-loop --last-verdict satisfied

Self-contained agent-overview.html (inline CSS, theme-aware, no external assets) — shareable as-is.

Suggest the next moves.
```
python3 scripts/upgrade_suggester.py --sheet ./my-agent/build-sheet.json --top 2
```
Ranks recorded deferrals (v1 before v2, real-integration first) plus standing hardening (tighten networking, pin the agent version, nest an outcome).
Finalize. Ensure NEXT-DIRECTIONS.md is current (Phase-4 tool), then goal_state.py advance → phase=done.

Hard rules

Recap what's actually live — read it from the sheet + goal state, never assert primitives that weren't created.
The overview is single-file — no external assets, so it shares cleanly.
Every next move names the exact mechanism.

"Confirm what's live vs still a plan?" Recommend: inventory from the sheet. Cite: this SKILL.
"Which single upgrade has the highest payoff?" Recommend: the top-ranked v1 deferral. Cite: upgrade_suggester ranking.
"Is the overview page current?" Recommend: regenerate after any change. Cite: this SKILL.

Tools

scripts/primitives_inventory.py — recap every owned primitive.
scripts/overview_page.py — regenerate single-file agent-overview.html.
scripts/upgrade_suggester.py — next 1–2 upgrades with mechanisms.

Read the full file on GitHub · 65 lines

Files

What ships with it

4 files 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.

Changes

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.

today First seen · 65 lines · 150 tokens per session scan A 77089d2d96ff

Subscribe to this mod's changes

wrap-up is a skill published in the GitHub repository alirezarezvani/claude-skills (28,607 stars, last pushed yesterday), licensed MIT. It adds 150 tokens to every session and 765 once invoked, about $0.0006 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-10-24.

Building agents Planning agentic-ai anthropic-claude claude-ai claude-code-skills claude-skills

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens