wrapup

A session wrap-up command that summarizes completed work, decisions, findings, and unresolved issues.

In plain words
What is it for?
Use it at the end of a session to update planning files and optionally offer key items to the team log.
Why use it?
It gives you a concise record of where a coding session ended and what should happen next.

Command

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 commands/bluzername/claude-code-power-stack/wrapup
Clone the repo
git clone --depth 1 https://github.com/bluzername/claude-code-power-stack
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 321 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.00000 $0.00321
Opus 5 $0.00000 $0.00161
Sonnet 5 $0.00000 $0.00064
Haiku 4.5 $0.00000 $0.00032

Measured yesterday against content hash f04ece667835, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

wrapup 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 yesterday.

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.

commands/wrapup.md · 54 lines

What it actually says

/wrapup - End-of-session summary and team log

Summarize what was accomplished in this session and offer to log key items for the team.

Steps

1. Summarize the session

Review the current conversation and identify:

  • Decisions made
  • Things completed
  • Unresolved issues or blockers
  • Findings worth sharing

2. Update planning files if active

If task_plan.md exists in the current directory:

  • Mark completed phases as complete
  • Update progress.md with a session summary
  • Note any new errors or decisions in task_plan.md

3. Present the wrapup

Wrapup - {today's date}
========================

Done:
- {what was completed}

Decisions:
- {key decisions made and why}

Open:
- {unresolved items, things to pick up next}

Keep it concise - 5-10 lines.

4. Offer to log for the team

If .team/log.jsonl exists (team mode is active), ask:

"Want me to log any of these for the team? I'd suggest:

  • [done] {completed item}
  • [decision] {key decision}
  • [blocker] {if any}"

If the user confirms, run ccs team log for each entry. Then remind them to run ccs team sync to share.

5. Suggest session name

If the session hasn't been named yet, suggest a name using the /rename-session convention so it's findable later.

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. yesterday First seen · 54 lines · 0 tokens per session scan A f04ece667835

Subscribe to this mod's changes

wrapup is a command published in the GitHub repository bluzername/claude-code-power-stack (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 321 tokens. 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.