A command that creates a weekly report from improvement-tracking files and learning notes across projects. It summarizes recent activity, code changes, inactive projects, busy days, recurring patterns, and suggested next actions.

Use it for a retrospective covering the last seven days or another number of days, including project activity, unusually large changes, recurring issues, and areas to continue or stop.

It turns scattered project metrics and daily notes into a short review of what changed and what may need attention.

retro — Command for Claude Code by Achitokun14

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.

Clone the repo

git clone --depth 1 https://github.com/Achitokun14/claude-universal

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/achitokun14/claude-universal/retro.svg)](https://agentmods.dev/commands/achitokun14/claude-universal/retro)

Your own site

<a href="https://agentmods.dev/commands/achitokun14/claude-universal/retro"><img src="https://agentmods.dev/badge/commands/achitokun14/claude-universal/retro.svg" alt="Measured on agentmods" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 409 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.

Model	Per session	Once invoked
Fable 5.1	$0.00019	$0.00409
Opus 5	$0.00010	$0.00204
Sonnet 5	$0.00004	$0.00082
Haiku 4.5	$0.00002	$0.00041

Measured 6d ago against content hash 296cf1c8cfe8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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.

user/commands/retro.md · 33 lines

What it actually says

Run a retrospective for the last N days (default: 7, pass a number via $ARGUMENTS to override).

Steps:

Find every IMPROVEMENT_STATE.json on this machine (user Desktop projects):

find ~/Desktop -maxdepth 5 -name IMPROVEMENT_STATE.json -not -path "*/node_modules/*" 2>/dev/null

For each, read the iterations array and filter entries where timestamp is within the last N days.
Aggregate and produce a report:
- Projects worked on this period: count by project, sorted by iteration count
- Biggest-delta projects: top 3 projects by total git line changes (sum dirty_files etc.)
- Quiet projects: projects with state files but 0 iterations in N days (candidates for archive)
- Session hot-streaks: days with 5+ total iterations across all projects
Read the relevant slice of ~/Desktop/ACTIVITIES/llm-wiki/YYYY-MM-DD.md files for the same N-day window. Extract:
- Top tagged patterns (#bug, #insight, #learning)
- Recurring URLs or packages from useful-resources.md
End with 3 recommendations:
- one thing to double down on (highest-velocity area)
- one thing to investigate (suspicious pattern)
- one thing to drop (graveyard candidate)

Format the output as a concise markdown report, <300 lines. Save it to ~/Desktop/ACTIVITIES/llm-wiki/weekly/$(date +%Y-W%V).md and print a summary to chat.

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.

6d ago First seen · 33 lines · 19 tokens per session scan A 296cf1c8cfe8

Subscribe to this mod's changes

retro is a command published in the GitHub repository Achitokun14/claude-universal (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 409 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.

Claude Code Planning ai-agents bash codex coding-agents gemini-cli

retro

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

init

milestone-list

fix

handoff

amp-identity

recall