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 codebygarv/Ai-skills --skill retro-facilitatorgit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/retro-facilitator)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/retro-facilitator"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/retro-facilitator.svg" alt="Measured on agentmods" 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.00047 | $0.00502 |
| Opus 5 | $0.00023 | $0.00251 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
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 8d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Turn raw retro input (a scattered list of what went well, what didn't, and ideas to try) into a structured summary with clustered themes and concrete, ownable action items — so retros produce follow-through instead of just catharsis.
When to Use
- After a sprint/iteration retro, with raw notes (sticky notes, a shared doc, verbal notes) that need structuring.
- A team's retros tend to surface the same complaints repeatedly with no visible action — worth using this to force clustering and concrete actions.
What to Analyze / Do
- Cluster related raw items into themes — several individually-worded complaints about "too many meetings," "context switching," "no focus time" likely cluster into one theme (interruption/focus-time issues), not three separate items.
- Separate went-well from went-poorly from ideas-to-try clearly.
- Convert the most significant themes into concrete action items — not every theme needs an action (some are just useful signal), but recurring or high-impact ones should get one.
- Flag recurring themes explicitly if this is a repeat topic from a prior retro (only if that context is provided) — a theme that keeps coming back with no action is itself worth surfacing.
- Keep action items scoped and ownable — "communicate better" isn't actionable; "add a 15-min daily written status update in the team channel" is.
Output Format
- Went Well — clustered, brief.
- Went Poorly — clustered into themes, not a flat list of every raw complaint.
- Ideas to Try — clustered.
- Action Items — table: Action | Owner (if assigned in the retro) | Related theme.
- Flag any theme noted as recurring, if prior-retro context was given.
Avoid
- Producing an action item for every single raw note — cluster first, act on the themes that matter most.
- Vague action items that can't be checked off as done or not done.
- Softening a genuinely negative theme into vague positive-sounding language — accurate clustering matters more than making the summary feel nice.
What ships with it
2 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.
- 8d ago First seen · 36 lines · 47 tokens per session scan A e9af128c8491
retro-facilitator is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 18d ago), licensed MIT. It adds 47 tokens to every session and 502 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-30.
Other skills, from other repositories
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…