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 yuusakuri/agent-skills --skill retrogit clone --depth 1 https://github.com/yuusakuri/agent-skillsWrote 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/yuusakuri/agent-skills/retro)<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/retro"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/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/yuusakuri/agent-skills/retro"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/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.00052 | $0.00693 |
| Opus 5 | $0.00026 | $0.00347 |
| Sonnet 5 | $0.00010 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
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 3d 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.
This is a copy
100% identical to retro — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective Facilitator
Run a structured retrospective that surfaces insights and produces actionable improvements.
Context
You are facilitating a retrospective for $ARGUMENTS.
If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.
Instructions
-
Choose a retro format based on context (or let the user pick):
Format A — Start / Stop / Continue:
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What's working well that we should keep?
Format B — 4Ls (Liked / Learned / Lacked / Longed For):
- Liked: What did the team enjoy?
- Learned: What new knowledge was gained?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Format C — Sailboat:
- Wind (propels us): What's driving us forward?
- Anchor (holds us back): What's slowing us down?
- Rocks (risks): What dangers lie ahead?
- Island (goal): Where are we trying to get to?
-
If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):
- Group similar items into themes
- Identify the most frequently mentioned topics
- Note sentiment patterns (frustration, energy, confusion)
-
Analyze the sprint performance:
- Sprint goal: achieved or not?
- Velocity vs. commitment (over-committed? under-committed?)
- Blockers encountered and how they were resolved
- Collaboration patterns (what worked, what didn't)
-
Generate prioritized action items:
Priority Action Item Owner Deadline Success Metric 1 [Specific, actionable improvement] [Name/Role] [Date] [How we'll know it worked] - Limit to 2-3 action items (more won't get done)
- Each must be specific, assignable, and measurable
- Reference previous retro actions if available — were they completed?
-
Create the retro summary:
## Sprint [X] Retrospective — [Date] ### Sprint Performance - Goal: [Achieved / Partially / Missed] - Committed: [X pts] | Completed: [Y pts] ### Key Themes 1. [Theme] — [summary] ### Action Items 1. [Action] — [Owner] — [By date] ### Carry-over from Last Retro - [Previous action] — [Status: Done / In Progress / Not Started]
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.
- 3d ago First seen · 77 lines · 52 tokens per session scan A 9ca1986756ce
retro is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 693 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to retro, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.