session-wrap

session-wrap is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 45 tokens per session (893 once invoked), scanned A, original, MIT.

An end-of-session record that saves important engineering decisions and creates a handoff document. A handoff explains the current work so another person or a later session can continue it.

In plain words
What is it for?
It is for closing a development session, preserving decisions, recording current Git and task state, and handing work to another engineer.
Why use it?
It prevents decisions, unfinished tasks, and repository context from being lost when a coding session ends. It puts both a machine-readable decision log and a readable summary in the project.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit It is for closing a development session, preserving decisions, recording current Git and task state, and handing work to another engineer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzapixl/pixl-ai/session-wrap
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 hamzaPixl/pixl-ai --skill session-wrap
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 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.

agentmods badge for session-wrap

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/session-wrap/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/session-wrap)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/session-wrap"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/session-wrap/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.

agentmods 80×15 button for session-wrap

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/session-wrap"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/session-wrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 893 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00893
Opus 5.5 $0.00018 $0.00357
Sonnet 5.5 $0.00009 $0.00179
Haiku 4.5 $0.00005 $0.00089

Measured 1mo ago against content hash ae1b999f2432, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

session-wrap 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.

packages/crew/skills/session-wrap/SKILL.md · 126 lines

How it starts

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

Overview

Combines decision capture and session handoff into a single end-of-session workflow. Produces two outputs:

  1. Decisions appended to .claude/memory/decisions.jsonl
  2. Handoff document at .context/session-handoff-{date}.md

Step 1: Gather Context

Git State

  1. Run git status to get current branch and working tree state
  2. Run git diff --stat for a summary of changed files
  3. Run git log --oneline -20 for recent commit history

Task State

  1. Call TaskList to get current task state
  2. For each in-progress or pending task, call TaskGet for full details

Memory Context

  1. Check if .claude/memory/decisions.jsonl exists — create if missing
  2. Read last 5 entries from decisions.jsonl (if any) to avoid duplicates
  3. Check if .claude/memory/sessions/ has recent summaries — read the latest

Key Files

  1. Identify the most important files from the git diff and task descriptions

Step 2: Extract Decisions

Review the session and identify decisions in these categories:

Category Examples
Architecture Chose pattern X over Y, added new module, restructured
Technology Added dependency, chose library, configured tool
Convention Established naming rule, coding standard, file structure
Trade-off Accepted limitation, deferred work, chose simpler approach
Bug fix Root cause identified, fix strategy chosen

For each decision, capture:

  • what: One-line summary (under 80 characters)
  • why: Rationale (1-2 sentences, under 200 characters)
  • context: Files or areas affected
  • category: One of architecture, technology, convention, trade-off, bugfix

Append each as a single JSON line to .claude/memory/decisions.jsonl:

{"date":"2026-03-08","category":"architecture","what":"Added schema-audit skill","why":"Prompt analysis showed DB schema review as top uncovered workflow","context":"skills/schema-audit/"}

If pixl is available (command -v pixl), also persist each decision as a pixl artifact:

pixl artifact put --name "decision-<category>-$(date +%s)" --type decision --content '<json>'

Read the full file on GitHub · 126 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. 1mo ago First seen · 126 lines · 45 tokens per session scan A ae1b999f2432

Subscribe to this mod's changes

session-wrap is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 893 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

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