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 koolamusic/claudefiles --skill retrogit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/retro)<a href="https://agentmods.dev/skills/koolamusic/claudefiles/retro"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/retro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/koolamusic/claudefiles/retro"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/retro.svg" alt="Reviewed on agentmods" width="80" 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.00134 | $0.02602 |
| Opus 5 | $0.00067 | $0.01301 |
| Sonnet 5 | $0.00027 | $0.00520 |
| Haiku 4.5 | $0.00013 | $0.00260 |
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 today.
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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective Skill
Generate honest, structured retrospectives for any Claude Code project. Retrospectives are the primary communication channel between engineering execution and product/stakeholder visibility.
Core Principles
- Adapt to the project — A 3-commit side project and a 50-phase enterprise migration both get useful retrospectives.
- Honest by default — Surface deviations, bugs, wrong assumptions, and scope surprises prominently. Never omit negative findings.
- Composable providers — Read from jira, git, GitHub, and the user. Never write to
.project/or modify git history. - Idempotent — Running
/retro 1twice overwrites the previous output. No duplicates. - Manual fills the gaps — For anything automation can't derive, ask the user.
Commands
| Command | Description |
|---|---|
/retro |
Retrospective for the most recently completed phase |
/retro <N> |
Retrospective for phase N |
/retro config |
Show current config and allow edits |
/retro status |
Show which phases have retros, which are pending, gaps |
/retro init |
Initialize retrospective infrastructure |
Execution Flow
1. Load or Initialize Config
Read .claude/retrospective.config.json. If missing, run first-run initialization (see references/config.md for schema and first-run behavior).
1.5. Detect Jira Workflow
Probe for .jira/STATE.md at the project root. If absent, skip this step.
If found, the repo uses the jira plugin for sprint state. This skill does not read .jira/sprints/* files — that coupling lives inside /jira:retro, which knows how to interpret CONTEXT.md (locked decisions D-XX), VERIFICATION.md (goal-backward outcomes), and per-wave PLAN files.
Surface this to the user via AskUserQuestion before proceeding:
Detected .jira/ — this repo uses the jira plugin for sprint state.
For per-sprint retros, /jira:retro <sprint-slug> is the right tool —
it reads BRIEF.md, CONTEXT.md, every *-PLAN.md, EXECUTION.md, and
VERIFICATION.md for that sprint.
/retro here covers cross-sprint rollups via git + github only — it
intentionally does NOT open jira's per-sprint files.
What ships with it
8 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.
- today First seen · 214 lines · 134 tokens per session scan A d2c2f4871c35
retro is a skill published in the GitHub repository koolamusic/claudefiles (131 stars, last pushed yesterday), licensed MIT. It adds 134 tokens to every session and 2,602 once invoked, about $0.0007 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-09-20.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…