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 agentmods add skills/hoavdc/codexkit/codexkit-scrum-retrospectivenpx skills add hoavdc/CodexKit --skill codexkit-scrum-retrospectivegit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-scrum-retrospective)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-scrum-retrospective"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-scrum-retrospective.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 | $0.00067 | $0.00977 |
| Opus 5 | $0.00034 | $0.00489 |
| Sonnet 5 | $0.00013 | $0.00195 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
codexkit-scrum-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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective Facilitator
Purpose
Turn sprint reflections into structured improvement actions by choosing the right retrospective format, guiding the session, and producing trackable outcomes.
When to use
- after every sprint to reflect on process and teamwork
- when team morale or velocity is declining and root causes are unclear
- when previous retro action items keep recurring without resolution
- when onboarding a new Scrum Master who needs facilitation structure
When not to use
- individual performance evaluation or disciplinary review
- project-level strategic retrospectives (use lessons-learned skill)
- mid-sprint debugging sessions
Inputs
- sprint number and duration
- sprint goal and whether it was met
- velocity or throughput data (current + last 3 sprints)
- previous retro action items and their completion status
- team size and maturity level (forming / storming / norming / performing)
- any specific incidents or friction points to address
Procedure
- Select format based on team maturity:
- Forming (< 3 sprints): Start / Stop / Continue
- Storming (3–10 sprints): 4Ls — Liked, Learned, Lacked, Longed For
- Norming (stable team): Sailboat — Wind / Anchors / Rocks / Island
- Performing (high trust): Lean Coffee, ORID, Timeline Retro
- Crisis / specific problem: Fishbone + 5 Whys
- Set the stage (10 min): Run ESVP check (Explorer/Shopper/Vacationer/Prisoner), review working agreements, safety check (1–5 scale).
- Gather data (20 min): Build sprint timeline of key events, review velocity trend and defect rate.
- Generate insights (25 min): Dot voting (3 dots per person), affinity clustering, 5 Whys on top-voted issue.
- Decide actions (25 min): Maximum 3 action items. Each: What + Who + Done-by-when + Success criteria. Check carryover from last retro.
- Close (10 min): Team health pulse (1–5 on 3 dimensions), appreciation round, retro-of-the-retro score.
Output
- retro summary with format used and key data gathered
- action items table: What | Owner | Due Date | Success Criteria | Status
- team health index trend (tracked across sprints)
- carryover escalation if same item recurs 3+ times without resolution
What ships with it
1 file 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.
- yesterday First seen · 95 lines · 67 tokens per session scan A 085746282437
codexkit-scrum-retrospective is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 977 once invoked, about $0.0003 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-03.
Other skills, from other repositories
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
developer_review
Code-review workflow for Developer Studio repositories.
building-agent-systems
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt injection, jailbreak defense, output filtering), RAG architecture (chunking, hybrid retrieval, rerank), and prompt…
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.
generating-docs
Generates README.md and DESIGN.md scaffolds by analyzing module structure. Use when creating documentation templates for new modules. Automatically triggered at module creation.