sessions:summarize

A command for replacing basic session summaries with AI-generated summaries.

In plain words
What is it for?
Use it to summarize one session or many sessions, set a processing limit, or choose a rule-based summary without AI services.
Why use it?
It makes imported or incomplete session records easier to understand and review.

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/iam-dev/cc-sessions/sessions-summarize
Clone the repo
git clone --depth 1 https://github.com/iam-dev/cc-sessions
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 310 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.00017 $0.00310
Opus 5 $0.00009 $0.00155
Sonnet 5 $0.00003 $0.00062
Haiku 4.5 $0.00002 $0.00031

Measured 2d ago against content hash 6c804eeea14b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sessions:summarize 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.

commands/sessions-summarize.md · 51 lines

What it actually says

Summarize Sessions

Regenerate AI-powered summaries for imported sessions.

Usage Examples

/sessions:summarize
/sessions:summarize --all
/sessions:summarize --all --limit 9999
/sessions:summarize mem_abc123_xyz789
/sessions:summarize --no-ai

Instructions

When the user runs /sessions:summarize, execute via CLI:

node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" summarize $ARGUMENTS

Arguments:

  • [sessionId] - Optional session ID to summarize a specific session
  • --all - Regenerate all sessions, not just those with rule-based summaries
  • --no-ai - Use rule-based summarizer only (no AI providers)
  • --limit <number> - Maximum number of sessions to process (default: 50)

Default Behavior

Without arguments, only sessions with rule-based (no-ai-summary) summaries are processed. Use --all to force regeneration of all sessions.

Success Output

Display the CLI output directly to the user, which will show progress and a summary of how many sessions were processed.

Error Messages

If no sessions need summarizing:

No sessions found that need AI summarization.

Use --all to regenerate summaries for all sessions.
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 · 51 lines · 17 tokens per session scan A 6c804eeea14b

Subscribe to this mod's changes

sessions:summarize is a command published in the GitHub repository iam-dev/cc-sessions (2 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 310 once invoked, about $0.0001 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.