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 tomzx/agents --skill run-retrospectivegit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/run-retrospective)<a href="https://agentmods.dev/skills/tomzx/agents/run-retrospective"><img src="https://agentmods.dev/badge/skills/tomzx/agents/run-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/tomzx/agents/run-retrospective"><img src="https://agentmods.dev/badge/skills/tomzx/agents/run-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.00036 | $0.00470 |
| Opus 5.5 | $0.00014 | $0.00188 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
run-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 22d 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.
What it actually says
Run Retrospective
Turns a completed initiative, a sprint, or a killed bet into organizational knowledge.
Produces a learning record in .pdlc/learnings/.
A kill without a retrospective wastes the effort — the point of killing is to learn cheaper than building would have taught.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. - A concluded initiative (shipped, iterated, or killed), or a sprint boundary.
Steps
- Frame the scope: which initiative or period, and what outcome occurred (shipped, iterated, killed).
- Capture what to keep (what worked and should be repeated), what to stop (what to never do again), and what to start (new actions to try).
- For each item, name the root cause, not just the symptom. "We were slow" is a symptom; "discovery and build ran in series with no handoff contract" is a root cause.
- Tie each learning back to the artifact chain: which assumption, decision, or gate should have caught this earlier?
- Convert the strongest start/stop items into concrete next actions with owners (feed the roadmap or a new initiative).
- Write the record to
.pdlc/learnings/N-<slug>.md.
Output Format
Use the template at skills/pdlc/templates/learning.md.
Keep/stop/start sections, each item with root cause and (where relevant) a traceable artifact link.
Outcome
If $OUTCOME_YAML is set, emit verdict: captured.
Completion Checklist
- Keep / stop / start each populated
- Each item has a root cause, not just a symptom
- Learnings traced back to the artifact chain where possible
- Strongest items converted to owned actions
Next Step
Feed owned actions into build-roadmap or a new /pdlc discover cycle.
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.
- 22d ago Changed · +4 lines 70f4a44fc7f4
- 24d ago Changed 96676c627fa8
- 1mo ago First seen · 43 lines · 36 tokens per session scan A 82f634a1c4ae
run-retrospective is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 470 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
gsd-milestone-summary
Generate a comprehensive project summary from milestone artifacts for team onboarding and review.
git-pr-workflows-onboard
Plan technical onboarding with environment setup, codebase orientation, team integration, and learning milestones. Use when helping developers join a project or preparing onboarding materials.
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
mentor
Draft a teaching-register comment on a GitHub issue or PR thread on the configured repo, aimed at a contributor missing context the maintainer would spell out. Reads the thread, decides whether an intervention is warranted, drafts one comment per the tone guide and convention pointers, and waits for explicit…
product-adoption
Diagnose and design product adoption for onboarding, activation, behavior change, feature discovery, rollout, and sustained use after launch. Covers consumer, B2B, internal-tool, and public-service contexts with evidence-based decision points and cohort segmentation. Does not own acquisition campaigns or marketing…
book-club
A structured workflow for running a book club, covering book selection, scheduling, preparation, discussion, and planning the next meeting.