summarize

summarize is a command for Claude Code from Fomo-Driven-Development/strategic-claude-base. It costs 10 tokens per session (2,135 once invoked), scanned A, original, MIT.

A command that summarizes the current implementation session by focusing on problems, unfinished work, and outstanding issues. It examines uncommitted changes in the repository.

In plain words
What is it for?
Use it after coding work to review the current Git changes, or provide a plan reference for a plan-specific summary.
Why use it?
It prevents important gaps from being buried in a general progress summary. If there are no uncommitted changes, it tells you that and asks what should be summarized instead.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md; positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Read(./**), Write(./.strategic-claude-basic/summary/**), Bash(git:*, date:*, grep:*), Glob.

Good fit Use it after coding work to review the current Git changes, or provide a plan reference for a plan-specific summary.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-base
agentmods
npx agentmods add commands/fomo-driven-development/strategic-claude-base/summarize

Made for: Claude Code.

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 summarize

README.md
[![agentmods](https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/summarize/github.svg)](https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/summarize)
Your own site
<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/summarize"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/summarize/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 summarize

Your own site · 80×15
<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/summarize"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/summarize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,135 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.00010 $0.02135
Opus 5.5 $0.00004 $0.00854
Sonnet 5.5 $0.00002 $0.00427
Haiku 4.5 $0.00001 $0.00214

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

Security

Grade A, and why

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 2mo 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.

.strategic-claude-basic/core/commands/summarize.md · 298 lines

How it starts

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

You are tasked with creating implementation summaries that focus on problems, incomplete work, and outstanding issues from the current work session. You should be problem-focused, session-scoped, and work only with uncommitted changes and current context.

Plan reference (optional): $1

Initial Response

When this command is invoked:

  1. Check for uncommitted work first:

    git status --porcelain
    
  2. If uncommitted changes exist, proceed immediately to context analysis

  3. If there are no uncommitted changes, respond with:

    I don't see any uncommitted changes in your repository.
    
    A summary documents the problems and incomplete work from your current implementation session.
    
    Please:
    1. Complete some implementation work, or
    2. Specify what you'd like me to summarize if you've already committed your changes
    
    Usage: `/summarize` - Auto-detect current work
    Usage: `/summarize PLAN_0001_...` - Summarize work for specific plan
    

Process Steps

Step 1: Current Session Context Analysis

  1. Check uncommitted changes:

    # Check what files were modified in current session
    git status --porcelain
    
    # Get detailed changes
    git diff
    git diff --cached
    
  2. Analyze the current conversation context:

    • Review what work was just completed in this chat session
    • Identify if a specific plan was being followed
    • Note any tests that were run and their results
    • Track any problems encountered during implementation
  3. Search for associated plan document:

    • If plan reference was provided as $1, use that
    • Otherwise, look in .strategic-claude-basic/plan/ for recent plans
    • Check conversation context for plan references
    • Look at file changes to infer what feature was being worked on
  4. Determine summary scope:

    Found uncommitted changes in [N] files.
    
    Based on the session context, I can see you were working on: [brief description]
    
    [If plan found]: This appears to be implementing Plan: [plan filename]
    [If no plan]: This appears to be standalone implementation work
    
    I'll create a summary focusing on problems and incomplete work from this session.
    Proceeding with summary generation...
    

Read the full file on GitHub · 298 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. 2mo ago First seen · 298 lines · 10 tokens per session scan A c10280847a02

Subscribe to this mod's changes

summarize is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 11mo ago), licensed MIT. It adds 10 tokens to every session and 2,135 once invoked, about $0.0000 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-08-31.