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 The-AI-Directory-Company/agents-and-skills --skill sprint-retrospectivegit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/sprint-retrospective)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/sprint-retrospective"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sprint-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/the-ai-directory-company/agents-and-skills/sprint-retrospective"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/sprint-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.00031 | $0.01408 |
| Opus 5.5 | $0.00012 | $0.00563 |
| Sonnet 5.5 | $0.00006 | $0.00282 |
| Haiku 4.5 | $0.00003 | $0.00141 |
Grade A, and why
sprint-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 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retrospective
Before you start
Gather the following from the facilitator. If anything is missing, ask before proceeding:
- Sprint duration and dates — What period are we reflecting on?
- Team size and composition — How many participants? Are there remote members?
- Sprint goal and outcome — Was the goal met, partially met, or missed?
- Key events — Any incidents, launches, scope changes, or team changes during the sprint?
- Previous action items — What did the team commit to last retro? Were they completed?
- Known tensions — Any interpersonal or process friction the facilitator is aware of?
Retrospective template
1. Review Previous Action Items (5 minutes)
Start every retro by reviewing last sprint's commitments. For each item:
Action Item: [Description]
Owner: [Name]
Status: Completed / In Progress / Not Started / Abandoned
Result: [What happened — measurable outcome if available]
If more than half of previous action items were not completed, address that pattern before gathering new data. Chronic non-completion means the team is overcommitting or under-prioritizing retro outcomes.
2. Choose a Facilitation Format
Select one format based on the team's current needs:
Start/Stop/Continue — Best for teams new to retros or when things are generally stable.
- Start: What should we begin doing?
- Stop: What should we stop doing?
- Continue: What is working and should not change?
4Ls (Liked, Learned, Lacked, Longed For) — Best when the team needs to reflect on growth. Four quadrants: what went well, what was discovered, what was missing, what was wished for.
Mad/Sad/Glad — Best when there is emotional tension or team morale is a concern. Surfaces feelings before jumping to process fixes.
Timeline — Best after a complex sprint with many events. Plot events chronologically, then annotate with energy levels and observations.
Rotate formats every 3-4 sprints to prevent staleness. Never use the same format more than 3 times in a row.
What ships with it
4 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.
- 1mo ago First seen · 129 lines · 31 tokens per session scan A c0faad69461d
sprint-retrospective is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 1,408 once invoked, about $0.0001 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
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
process-flowchart-designer
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.