wrap-up

wrap-up is a skill for Claude Code, Codex from anthropics/launch-your-agent. It costs 105 tokens per session (1,395 once invoked), scanned A, original, Apache-2.0.

A checklist for closing or revisiting a Claude Managed Agent project, including its overview, owned building blocks, run history, status, next improvements, and setup hygiene.

In plain words
What is it for?
Use it to review an agent's files and evaluations, archive sessions, check secret storage, review deployments, and identify the next one or two upgrades.
Why use it?
It makes the finished agent easier to understand and catches common cleanup issues before handoff.

Skill for Claude CodeCodex

About the project

Launch Your Agent is a Claude Code skill that guides a founder through building and deploying a managed agent in their own Claude account. It interviews the user, defines an initial version, launches and evaluates it, then helps iterate or schedule it. The catalogue skills provide this guided workflow.

anthropics/launch-your-agent · 980 stars · on GitHub

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.

agentmods
npx agentmods add skills/anthropics/launch-your-agent/wrap-up
Any agent
npx skills add anthropics/launch-your-agent --skill wrap-up
Clone the repo
git clone --depth 1 https://github.com/anthropics/launch-your-agent

Made for: Claude Code, Codex.

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.

agentmods badge for wrap-up

README.md
[![agentmods](https://agentmods.dev/badge/skills/anthropics/launch-your-agent/wrap-up.svg)](https://agentmods.dev/skills/anthropics/launch-your-agent/wrap-up)
Your own site
<a href="https://agentmods.dev/skills/anthropics/launch-your-agent/wrap-up"><img src="https://agentmods.dev/badge/skills/anthropics/launch-your-agent/wrap-up.svg" alt="Measured on agentmods" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,395 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00105 $0.01395
Opus 5 $0.00053 $0.00698
Sonnet 5 $0.00021 $0.00279
Haiku 4.5 $0.00011 $0.00139

Measured 6d ago against content hash 4023fd1bba0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 6d 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.

.claude/skills/wrap-up/SKILL.md · 38 lines

How it starts

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

Wrap-up — celebrate it, show what they built, point at what's next

You are closing out (or checking in on) a founder's Claude Managed Agent. The tone is celebratory: they just shipped a managed agent that runs without them — say so, warmly, in one or two sentences ("🎉 you've shipped a managed agent — here's what you built"), then show them what they own and the one or two upgrades worth doing next. End on the overview page, not a wall of text. This is a moment, not a checklist read-out.

Follow the same voice rules as /launch-your-agent: warm, compact, tables for anything enumerable, primitives called by their real names (Outcome, Session, Deployment, Vault, Memory store) with a plain gloss on first use, the shared emoji shorthand (🤖 agent · 📦 environment · 🎯 outcome · ▶️ session · 🗓️ deployment · 🔌 connector · 🔐 vault · 🧠 memory store · 🧪 evals), no unverified timings. No cost notes — don't volunteer per-run or per-month spend figures; answer cost questions only if the founder asks.

1. Read the state

  • Read ./my-agent/: build-sheet.json, IDS.env, NEXT-DIRECTIONS.md, outcome.md, evals/, the existing agent-overview.html. (If there is no my-agent/ folder here, say so and stop — point them at /launch-your-agent.)
  • If my-agent/.env holds a key, source it and refresh live state via the API (shapes: ../launch-your-agent/references/cma-api.md): each session's status + outcome_evaluations[], deployment status + schedule.upcoming_runs_at, latest usage. Parse with python (strict=False), never jq.
  • No key → continue describe-only and say in one sentence that live status needs the key in .env.
  • A session still running → say so and ask (AskUserQuestion): wait for it, or wrap with what's done.
  • Nothing launched yet → wrap the plan only; everything below still applies but the status is "○ Planned".

2. Produce the wrap-up (in this order)

Read the full file on GitHub · 38 lines

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.

  1. 6d ago First seen · 38 lines · 105 tokens per session scan A 4023fd1bba0d

Subscribe to this mod's changes

wrap-up is a skill published in the GitHub repository anthropics/launch-your-agent (980 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,395 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens