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 hamzafarooq/claude-code-starter --skill retro-facilitatorgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/retro-facilitator)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/retro-facilitator"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/retro-facilitator/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/hamzafarooq/claude-code-starter/retro-facilitator"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/retro-facilitator.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.00046 | $0.00372 |
| Opus 5.5 | $0.00018 | $0.00149 |
| Sonnet 5.5 | $0.00009 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
retro-facilitator 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 1mo 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.
What it actually says
Ask the user:
- "Paste any notes from the sprint — what happened, what people said, anything relevant."
- "How long was the sprint and what was the goal?"
- "How many people on the team? Any themes you already know came up?"
Then produce:
Sprint Retrospective — [Sprint Name/Number]
Sprint goal: [what you set out to do] Goal status: Achieved / Partially achieved / Missed — [one line on why]
What went well
4–6 bullets. Specific things that worked — behaviors, practices, or moments worth repeating. Not generic ("good communication") — concrete ("daily standups stayed under 10 minutes").
What didn't go well
4–6 bullets. Be direct. Name the pattern, not just the symptom. Avoid blame — focus on systems and process.
Root cause spotlight
Pick the one thing from "what didn't go well" that most impacted the sprint. One paragraph: what happened, why it happened, what it cost.
Action items
| Action | Owner | Done by |
|---|---|---|
| [specific change to make — not "improve communication"] | [name or role] | [next sprint / specific date] |
Limit to 3 action items. More than 3 means none will get done.
Carry forward
Any unresolved themes from previous retros. Flag if the same issue has appeared 3+ times.
End with: "At the next retro, start by reviewing these 3 action items."
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.
- 1mo ago First seen · 42 lines · 46 tokens per session scan A 42ec1e6d46a8
retro-facilitator is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 372 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.