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.
npx skills add artem-from-ua/claude-plugins --skill retrogit clone --depth 1 https://github.com/artem-from-ua/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/artem-from-ua/claude-plugins/retro)<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>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.1 | $0.00056 | $0.00739 |
| Opus 5 | $0.00028 | $0.00369 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
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.
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:
{CLAUDE_PROJECT_DIR}/.claude-plugin/retroscope.json(project-level, preferred){CLAUDE_PROJECT_DIR}/.claude/retroscope.json(project-level, legacy fallback)~/.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:setupskill 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
sessionmode is available (no storage configured for today/yesterday). - Skip the mode question and use
sessionmode directly, showing a note: "💡 Tip: Run/retroscope:setupto 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, orinherit(default:haiku)extractMode— pre-filter sessions to text-only (default:true)sessionSource— data source for/retro session:logs(default) orcontextscope— report scope:project(default, current project only) orall(cross-project daily reports)autoPush— git push after commit (default:false)timezone— timezone for date calculations (default: system)
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.
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.
- 8d ago First seen · 63 lines · 56 tokens per session scan A 32f4be8cf166
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…