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.

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.

It makes the finished agent easier to understand and catches common cleanup issues before handoff.

How anthropics/launch-your-agent configures Claude Code

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 · 1,108 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to anthropics/launch-your-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/anthropics/launch-your-agent/main/.claude/skills/wrap-up/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/anthropics/launch-your-agent

Made for: Claude Code.

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/anthropics/launch-your-agent/wrap-up/github.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/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/anthropics/launch-your-agent/wrap-up"><img src="https://agentmods.dev/badge/skills/anthropics/launch-your-agent/wrap-up.svg" alt="Reviewed on agentmods" width="80" 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,394 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00105	$0.01394
Opus 5.5	$0.00042	$0.00558
Sonnet 5.5	$0.00021	$0.00279
Haiku 4.5	$0.00011	$0.00139

Measured 1mo ago against content hash 755b944a55ea, 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 1mo 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.

1mo ago Changed 755b944a55ea
2mo 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 (1,108 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,394 once invoked, about $0.0004 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-08-30.

Building agents Planning

wrap-up next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wrap-upanthropics/launch-your-agent	Skill	1.1k	1mo ago	Apache-2.0	A	105	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

launch-your-agent: Skill for Claude Code