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 cpliakas/claude-code-engineering-leaders --skill facilitate-retrospectivegit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/facilitate-retrospective)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/facilitate-retrospective"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/facilitate-retrospective/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/cpliakas/claude-code-engineering-leaders/facilitate-retrospective"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/facilitate-retrospective.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.00042 | $0.02268 |
| Opus 5 | $0.00021 | $0.01134 |
| Sonnet 5 | $0.00008 | $0.00454 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
facilitate-retrospective 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 10d 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.
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.
Facilitate Retrospective
Facilitate a structured retrospective that helps a team introspect a body of work and identify concrete improvements. The output follows the Derby-Larsen five-phase retrospective framework (Set the Stage, Gather Data, Generate Insights, Decide What to Do, Close the Retrospective) adapted for AI-assisted analysis.
Input
$ARGUMENTS = description of the body of work to retrospect — sprint number and team name, milestone description, date range, or a narrative summary of what was delivered and what happened.
Process
1. Handle Missing Input
If $ARGUMENTS is empty or contains no actionable description, prompt the team lead for the minimum information needed to begin. Present these questions in a single consolidated prompt:
- What work are we retrospecting? — Sprint number, milestone name, or date range.
- Who is the team? — Team name or composition (helps frame observations).
- What was delivered? — Key deliverables, features shipped, or goals targeted.
- What notable events occurred? — Incidents, blockers, surprises, scope changes, staffing changes, or process experiments.
Do not proceed until at least a work scope and one or more notable events or deliverables are provided.
2. Gather Context
- Read the project's CLAUDE.md for architecture, domain language, and team conventions
- Scan for a roadmap or backlog file if one exists (Glob for roadmap*, backlog*, TODO*)
- Check project memory for recent work completions, decisions, and open questions logged by the
product-owneragent - Check the Agile Coach's project memory
(
.claude/agent-memory/engineering-leaders-agile-coach/MEMORY.md) for a configuredretrospective_directorypath - If a directory is configured, read prior retrospective artifacts in that directory to identify patterns and recurring themes
3. Set the Stage
Establish the retrospective's scope and framing:
- Scope statement: What period or body of work is being reviewed (sprint dates, milestone name, or work description)
- Prime Directive: Frame the retrospective under the Retrospective Prime Directive — "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." This is not decorative; it is a structural constraint on the language used throughout the document.
- Blamelessness constraint: All observations, insights, and action items throughout the document must be framed in terms of systems and processes. No language may attribute outcomes to individual people.
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.
- 10d ago First seen · 214 lines · 42 tokens per session scan A 8bc9f5b17f0e
facilitate-retrospective is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 19d ago), licensed MIT. It adds 42 tokens to every session and 2,268 once invoked, about $0.0002 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.
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.