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 kazdenc/builder-skills --skill retrogit clone --depth 1 https://github.com/kazdenc/builder-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/kazdenc/builder-skills/retro)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/retro"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/retro.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.00070 | $0.01389 |
| Opus 5 | $0.00035 | $0.00694 |
| Sonnet 5 | $0.00014 | $0.00278 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
retro 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a retrospective that produces action items, not just observations. A retro without specific next steps is a venting session.
Principles — hold these throughout:
- Blame-free. Focus on systems, processes, and circumstances — not people. "The deploy process let a bug through" not "Bob broke prod."
- Actions over observations. Every theme must produce a concrete change. If it doesn't lead to action, note it and move on.
- Max 3 action items. More than three won't get done. Prioritize ruthlessly.
Step 1: Set Context
Establish the boundaries before gathering input:
| Question | Answer |
|---|---|
| What period/project? | Name it specifically — "Sprint 14" or "Billing v2 launch" |
| What was the goal? | What were we trying to accomplish? |
| What actually happened? | State the outcome factually — shipped on time, missed by 2 weeks, hit metrics, didn't |
| Who was involved? | List the team so contributions are visible |
| Timeline | Start date, end date, key milestones |
Write a 2-3 sentence summary: "We set out to [goal]. We [what happened]. The result was [outcome]."
If the user hasn't provided this context, ask for it. Don't fabricate project history.
Step 2: Gather Input — The 4Ls
Use the 4Ls framework to collect observations. Ask the user to contribute to each category:
| Category | Prompt | What goes here |
|---|---|---|
| Liked | What went well? What should we keep doing? | Practices, decisions, or moments that worked |
| Learned | What did we discover? What surprised us? | New knowledge, skills, or insights gained |
| Lacked | What was missing? What held us back? | Resources, information, tools, or processes we needed but didn't have |
| Longed For | What do we wish we had? What would make next time better? | Improvements, tools, practices, or changes we want |
Gathering tips:
- Ask for specifics, not generalities. "Liked: good communication" is useless. "Liked: daily 10-min standups kept everyone unblocked" is actionable.
- Aim for 3-5 items per category.
- If working async, give people a template to fill in before the session.
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 · 153 lines · 70 tokens per session scan A 73bf33f777c2
retro is a skill published in the GitHub repository kazdenc/builder-skills (45 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 1,389 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-08-30.
Other skills, from other repositories
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.
outcome-review
Review whether a funded product bet changed its intended outcome and append evidence-backed learning.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
roadmap-refresh
Refresh Now, Next, and Later from funded demand, objectives, dependencies, and delivery evidence.
stakeholder-brief
Prepare a concise owner or stakeholder brief with current decisions, evidence, bets, outcomes, roadmap, and provenance.