retro

retro is a skill for Claude Code from artem-from-ua/claude-plugins. It costs 56 tokens per session (739 once invoked), scanned A, original, MIT.

A command for summarizing Claude Code work from the current session or from all sessions on today’s or yesterday’s date.

In plain words
What is it for?
Use it to view a current-session summary or generate saved daily reports for today or yesterday, with an option to regenerate cached reports.
Why use it?
It turns session history into a concise review and can save daily reports for later reference.

Skill for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Part of the retroscope plugin — 2 skills shipped together

Good fit Use it to view a current-session summary or generate saved daily reports for today or yesterday, with an option to regenerate cached reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/artem-from-ua/claude-plugins/retro
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 artem-from-ua/claude-plugins --skill retro
Clone the repo
git clone --depth 1 https://github.com/artem-from-ua/claude-plugins

Made for: Claude Code.

Or install retroscope, the plugin that ships this one along with the rest of its 2 skills.

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 retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/retro.svg)](https://agentmods.dev/skills/artem-from-ua/claude-plugins/retro)
Your own site
<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/retro"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/retro.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 739 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.00056 $0.00739
Opus 5 $0.00028 $0.00369
Sonnet 5 $0.00011 $0.00148
Haiku 4.5 $0.00006 $0.00074

Measured 8d ago against content hash 32f4be8cf166, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

retro 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 8d 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.

plugins/retroscope/commands/retro/SKILL.md · 63 lines

How it starts

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

/retro — Session Retrospective Report

Generate a retrospective summary of Claude Code session(s).

Modes

Mode Description Storage
session Summarize current session from context Display only (not saved)
today Aggregate all today's sessions Saved to storage repo + git commit
yesterday Aggregate all yesterday's sessions Saved to storage repo + git commit

Add --force to any mode to regenerate even if a cached report exists (e.g., /retro today --force).

Step 1: Load Config

Look for config in this order:

  1. {CLAUDE_PROJECT_DIR}/.claude-plugin/retroscope.json (project-level, preferred)
  2. {CLAUDE_PROJECT_DIR}/.claude/retroscope.json (project-level, legacy fallback)
  3. ~/.claude/retroscope.json (user-level)

If no config found: ask the user whether to run setup now using AskUserQuestion:

  • Option A: "Yes, run setup now" → invoke /retroscope:setup skill and stop.
  • Option B: "No, continue without config" → continue with defaults (sessionSource: logs, display-only, no storage).

Step 2: Determine Mode

You MUST ask the user which mode they want. Do NOT skip this step or assume a default.

If the user provided a mode argument (e.g., /retro session, /retro today), use it. Otherwise use AskUserQuestion with options: session, today, yesterday.

Parse the user's argument for both mode and flags. If --force is present, set force = true and strip it from the mode argument before further processing.

If no config was found (user chose to continue without config):

  • Only session mode is available (no storage configured for today/yesterday).
  • Skip the mode question and use session mode directly, showing a note: "💡 Tip: Run /retroscope:setup to enable daily reports (today/yesterday)."

Config fields used:

  • storageDir — where to save reports (REQUIRED for today/yesterday)
  • language — report language (default: English)
  • model — report generation model: haiku, sonnet, or inherit (default: haiku)
  • extractMode — pre-filter sessions to text-only (default: true)
  • sessionSource — data source for /retro session: logs (default) or context
  • scope — report scope: project (default, current project only) or all (cross-project daily reports)
  • autoPush — git push after commit (default: false)
  • timezone — timezone for date calculations (default: system)

Read the full file on GitHub · 63 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 63 lines · 56 tokens per session scan A 32f4be8cf166

Subscribe to this mod's changes

retro is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 739 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens