Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From engram
engram: Generate a token savings report showing compression and redundancy statistics for the current session
npx claudepluginhub pythondatascrape/engram-ccode --plugin engramHow this skill is triggered — by the user, by Claude, or both
Slash command
/engram:reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a token savings report for the current session.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Breaks plans, specs, or PRDs into thin vertical-slice issues on the project issue tracker using tracer bullets. Useful for converting high-level work into grabbable implementation tickets.
Share bugs, ideas, or general feedback.
Generate a token savings report for the current session.
Call mcp__engram__get_stats with no arguments to retrieve the current session statistics.
Present the stats summary to the user, then ask:
Session Report — {today's date} (e.g. "Session Report — 2026-03-27").engram/savings-log.csv (default: yes)Check if .engram/config.yaml exists. If it does, read it and extract any pricing fields (pricing.model, pricing.input_per_1k). Pass those as arguments when calling the report tool.
Call mcp__engram__generate_report with:
name: the report name the user provideddescription: the description the user provided (omit if blank)savingsLogPath: if user said yes to saving, pass .engram/savings-log.csv; omit if they said nopricing: if config has pricing info, pass as { "model": "...", "inputPer1k": ... } (nested object)Display the full markdown report returned by the tool.
Ask: "Would you like to save this report as a markdown file?" If yes, ask for a filename (suggest engram-report-{date}.md) and write the report to that path in the current working directory.