agentmods.dev

retro

retro is a command for coding agents from koolamusic/claudefiles. It costs 25 tokens per session (868 once invoked), scanned A, original, MIT.

A command that creates a retrospective, which is a written review of completed work. It can review one sprint or combine lessons from work completed since a chosen date.

In plain words
What is it for?
Use it after a sprint or across a date range to record outcomes, what worked, delays, surprises, workflow changes, and concrete follow-ups.
Why use it?
It gathers project records and the human team's experience in one document so useful lessons and follow-up actions are not lost.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the jira plugin — 13 commands, 9 agents shipped together

not rated 132 6d ago A scan 25 tokens original MIT
View the source file koolamusic/claudefiles
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.

agentmods
npx agentmods add commands/koolamusic/claudefiles/retro
Clone the repo
git clone --depth 1 https://github.com/koolamusic/claudefiles

Or install jira, the plugin that ships this one along with the rest of its 13 commands, 9 agents.

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/commands/koolamusic/claudefiles/retro.svg)](https://agentmods.dev/commands/koolamusic/claudefiles/retro)
Your own site
<a href="https://agentmods.dev/commands/koolamusic/claudefiles/retro"><img src="https://agentmods.dev/badge/commands/koolamusic/claudefiles/retro.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 868 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.00868
Opus 5 $0.00013 $0.00434
Sonnet 5 $0.00005 $0.00174
Haiku 4.5 $0.00003 $0.00087

Measured 5d ago against content hash b74ae8a0f16d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 5d 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/jira/commands/retro.md · 75 lines

How it starts

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

Capture lessons from completed work. Two modes:

  • Per-sprint (default, or --sprint <slug>) — one RETRO.md inside the sprint dir
  • Rollup (--since <date>) — synthesize across all sprints since a date into .jira/retros/<date>.md

Per-sprint mode

  1. Resolve the sprint slug: --sprint <slug> or cat .jira/CURRENT. Stop if missing.

  2. Read BRIEF.md, CONTEXT.md, all *-PLAN.md files, EXECUTION.md, VERIFICATION.md, and REVIEW.md (if any exist).

  3. Use AskUserQuestion to elicit the human's view. Five tight questions, single message:

    • Outcome: shipped, partial, abandoned, other?
    • What worked best?
    • What slowed you down?
    • Biggest surprise?
    • Anything to change about the workflow itself?

    Treat the answers as raw input — do not paraphrase them.

  4. Write RETRO.md at .jira/sprints/<slug>/RETRO.md using the template at ${CLAUDE_PLUGIN_ROOT}/templates/sprint/RETRO.md. Combine:

    • Workflow signal from disk (commits made, deviations from EXECUTION.md, Nyquist gaps, review findings)
    • Human signal from AskUserQuestion (verbatim, attributed)

  5. Surface follow-ups. If the user named concrete actions, list them as a checklist at the bottom. Don't create new sprints — that's the user's call.

  6. Update STATE.md. Append any "Lessons for the workflow itself" to the ## Notes section (these accumulate across sprints).

  7. Commit:

    git add .jira/sprints/<slug>/RETRO.md .jira/STATE.md
git commit -m "retro(<slug>): <one-line outcome>"

Rollup mode (--since YYYY-MM-DD)

  1. Find sprints with directory dates ≥ <since>: ls .jira/sprints/ | awk -F- '{print $1"-"$2"-"$3" "$0}' | sort | awk -v d="<since>" '$1>=d {print $2}'.

  2. Read each sprint's BRIEF, PLAN, EXECUTION, RETRO (if RETRO exists; otherwise skip per-sprint retro and rely on plan/execution signal).

  3. Use AskUserQuestion with three rollup questions:

    • Across these sprints, what pattern keeps coming up — good or bad?
    • Which sprint had the biggest learning?
    • One change you'd commit to for the next batch?

Read the full file on GitHub · 75 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. 5d ago First seen · 75 lines · 25 tokens per session scan A b74ae8a0f16d

Subscribe to this mod's changes

retro is a command published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 868 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-30.

Project management
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens