wrap-up

An end-of-session procedure that checks whether the current plan and task list are complete, then follows the appropriate closing path. In a Git repository, it can also refresh repository state and clean up branches that no longer exist remotely.

In plain words
What is it for?
Use it when ending a coding session to run a brief retrospective, prepare a follow-up or resume prompt, refresh Git state, and remove obsolete branches when the work is complete.
Why use it?
It prevents unfinished work from being treated as complete and leaves clear instructions for continuing later.

Skill for Claude CodeCodex

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/dryvist/claude-code-plugins/wrap-up
Any agent
npx skills add dryvist/claude-code-plugins --skill wrap-up
Clone the repo
git clone --depth 1 https://github.com/dryvist/claude-code-plugins

Made for: Claude Code, Codex.

Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,219 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 $0.00096 $0.03219
Opus 5 $0.00048 $0.01610
Sonnet 5 $0.00019 $0.00644
Haiku 4.5 $0.00010 $0.00322

Measured 2d ago against content hash f6c513f8f7e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

ai-cli-harness-better-practices/skills/wrap-up/SKILL.md · 303 lines

How it starts

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

Post-Session Wrap-Up

State warning: TaskList contents, plan checklist state, and any branch or remote-tracking state all change between invocations. Re-gather them from Step 0; never trust prior outputs from this conversation.

/wrap-up has two paths. Step 0 decides which one runs.

Step 0 outcome Path
Plan complete OR no plan Path A — retrospective + follow-up prompt; plus repo refresh and branch cleanup when in a repository
Plan incomplete Path B — emit resume blocks; skip Path A cleanup entirely

The purge-pr focused mode (bottom of this file) bypasses Step 0 entirely.

Step 0: Determine session state

Invoke the /session-status skill to analyze the plan checklist, TaskList state, and gather unfinished work and issues.

Determine the completion outcome based on /session-status's report:

  • Path A (complete): Every TaskList task is complete (or empty), AND every plan-file checklist item is checked or complete (or no plan file exists).

    Additional Git Flow Requirementrepository only. Establish that first:

    git rev-parse --is-inside-work-tree >/dev/null 2>&1 || echo "not a repository"
    

    Outside a repository, skip this requirement entirely; completion is decided by the TaskList and plan checklist alone.

    Inside one, determine whether this is a git-flow repo (default branch develop). Run this as one block — the resolution and its use must share a shell (see ARCHITECTURE.md) — and take exactly one of three branches; this gate must never fail open:

    default_branch=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null)
    default_branch=${default_branch#origin/}
    [ -n "$default_branch" ] || default_branch=$(
      gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' 2>/dev/null)
    
    if [ -z "$default_branch" ]; then
      echo "BLOCKED: default branch unresolved; cannot confirm promotion state"
    elif [ "$default_branch" = develop ]; then
      git fetch origin --force develop main &&
        git log --oneline origin/main..origin/develop
    else
      echo "trunk repo — promotion requirement does not apply"
    fi
    

Read the full file on GitHub · 303 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. 2d ago First seen · 303 lines · 96 tokens per session scan A f6c513f8f7e2

Subscribe to this mod's changes

wrap-up is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 96 tokens to every session and 3,219 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-31.

Related

Other skills, from other repositories

rspec

This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…

hoblin/claude-ruby-marketplace · 125 tokens

activerecord

This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…

hoblin/claude-ruby-marketplace · 180 tokens

draper-decorators

This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…

hoblin/claude-ruby-marketplace · 131 tokens

mcp-server

This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…

hoblin/claude-ruby-marketplace · 98 tokens

ratatui-ruby

This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…

hoblin/claude-ruby-marketplace · 119 tokens

dragonruby

This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…

hoblin/claude-ruby-marketplace · 100 tokens