A command that closes a coding session by saving its state and optionally exporting metrics, creating a summary, and removing temporary files.

Use it to save open files, decisions, task progress, session metrics, summaries, and cleanup temporary files before ending work.

It prevents useful context and progress from being lost when work ends, while keeping optional records of what happened.

session-end — Command by sethdford

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/sethdford/flowx/session-end

Clone the repo

git clone --depth 1 https://github.com/sethdford/flowx

Made for: Claude Code.

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 553 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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	$0.00000	$0.00553
Opus 5	$0.00000	$0.00277
Sonnet 5	$0.00000	$0.00111
Haiku 4.5	$0.00000	$0.00055

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to session-end — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/hooks/session-end.md · 107 lines

What it actually says

hook session-end

Cleanup and persist session state before ending work.

Usage

npx claude-flow hook session-end [options]

Options

--session-id, -s <id> - Session identifier to end
--save-state - Save current session state (default: true)
--export-metrics - Export session metrics
--generate-summary - Create session summary
--cleanup-temp - Remove temporary files

Examples

Basic session end

npx claude-flow hook session-end --session-id "dev-session-2024"

With full export

npx claude-flow hook session-end -s "feature-auth" --export-metrics --generate-summary

Quick close

npx claude-flow hook session-end -s "quick-fix" --save-state false --cleanup-temp

Complete persistence

npx claude-flow hook session-end -s "major-refactor" --save-state --export-metrics --generate-summary

Features

State Persistence

Saves current context
Stores open files
Preserves task progress
Maintains decisions

Metric Export

Session duration
Commands executed
Files modified
Tokens consumed
Performance data

Summary Generation

Work accomplished
Key decisions made
Problems solved
Next steps identified

Cleanup Operations

Removes temp files
Clears caches
Frees resources
Optimizes storage

Integration

This hook is automatically called by Claude Code when:

Ending a conversation
Closing work session
Before shutdown
Switching contexts

Manual usage in agents:

# At session end
npx claude-flow hook session-end --session-id "your-session" --generate-summary

Output

Returns JSON with:

{
  "sessionId": "dev-session-2024",
  "duration": 7200000,
  "saved": true,
  "metrics": {
    "commandsRun": 145,
    "filesModified": 23,
    "tokensUsed": 85000,
    "tasksCompleted": 8
  },
  "summaryPath": "/sessions/dev-session-2024-summary.md",
  "cleanedUp": true,
  "nextSession": "dev-session-2025"
}

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.

yesterday First seen · 107 lines · 0 tokens per session scan A 711aacadf1b6

Subscribe to this mod's changes

session-end is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 553 tokens. A static security scan graded it A with 0 findings. It is 100% identical to session-end, differing in 12 lines, and is treated as a copy.

Analytics and metrics Planning

session-end