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 uthumany/uthy-legacy-os --skill retrospectivegit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/retrospective)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/retrospective"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/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/uthumany/uthy-legacy-os/retrospective"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/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.00039 | $0.00736 |
| Opus 5.5 | $0.00016 | $0.00294 |
| Sonnet 5.5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
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 2mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective
Overview
A retrospective is a structured reflection on what happened, why, and what to do differently next time. Done well, retros turn experience into improvement. This skill covers multiple retro formats, facilitation techniques, and turning findings into action.
When to Use
- After a product launch or major release
- At the end of a sprint or project
- When the team is stuck in the same patterns
- Building a culture of continuous improvement
- Don't use for: finger-pointing (that's a postmortem, not a retro), when the team is too burned out (fix the burn-out first)
Instructions
1. Choose the Format
Start/Stop/Continue (simple, gets results fast):
- Start: What should we start doing?
- Stop: What should we stop doing?
- Continue: What should we keep doing?
4Ls (good for medium-complexity projects):
- Liked: What worked well?
- Learned: What did we learn?
- Lacked: What was missing?
- Longed For: What do we wish we had?
Sailboat (good for emotional topics):
- Wind: What pushed us forward?
- Anchor: What held us back?
- Rocks: What risks do we see ahead?
- Sun: What are we excited about?
2. Gather Data (5 min per person)
- Each person writes their observations independently
- One observation per sticky/card
- Be specific: reference events, dates, and decisions — not vague feelings
- Timebox: 5 minutes max per section
3. Cluster and Discuss (10 min)
- Group related observations
- Discuss the most-voted clusters
- Focus on systems and processes, not people
- Ask "What led to that?" to find root causes
4. Identify Action Items (10 min)
For each key finding:
- Action: What specifically will we change?
- Owner: Who's responsible?
- Timeline: When will it be done?
- Success criteria: How will we know it worked?
5. Follow Up (next retro)
- Start the next retro by reviewing action items from the previous one
- Were they completed? Did they help? If not, why?
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.
- 2mo ago First seen · 93 lines · 39 tokens per session scan A 1544e9a6eed8
retrospective is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 736 once invoked, about $0.0002 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-08-31.
retrospective compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| retrospectiveuthumany/uthy-legacy-os | Skill | 5 | 5mo ago | MIT | A | 39 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |