Borrowing it
Nothing to install: this file belongs to cesarnml/son-of-anton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cesarnml/son-of-anton/main/.agents/skills/write-retrospective/SKILL.mdgit clone --depth 1 https://github.com/cesarnml/son-of-antonWrote 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/cesarnml/son-of-anton/write-retrospective)<a href="https://agentmods.dev/skills/cesarnml/son-of-anton/write-retrospective"><img src="https://agentmods.dev/badge/skills/cesarnml/son-of-anton/write-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/cesarnml/son-of-anton/write-retrospective"><img src="https://agentmods.dev/badge/skills/cesarnml/son-of-anton/write-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.00060 | $0.00720 |
| Opus 5.5 | $0.00024 | $0.00288 |
| Sonnet 5.5 | $0.00012 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
soa-write-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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Retrospective
Retrospectives are AI-readable artifacts first, human-readable second. Future agents read them at phase starts and epic planning to understand what patterns to repeat, what to avoid, and what the spec missed. Section naming must be consistent across retrospectives so agents can reliably extract signal.
Required Sections (in order)
1. Scope delivered
What shipped: PR numbers, branch name, scope items as a short list. One paragraph max. This is the factual anchor — without it the retro floats.
2. What went well
Patterns to repeat. Include why they worked, not just that they did. "TypeScript caught it" is noise. "TypeScript caught it because the type was narrow enough to make the error unambiguous at the call site" is signal. Aim for reusable lessons, not praise.
3. Pain points
Friction sources with root cause. Distinguish avoidable waste (something that could be designed away) from expected cost (inherent to the work). Both are worth recording but they imply different follow-up.
4. Surprises
Things not in the spec — good and bad. This is the highest-signal section for future AI readers: surprises are exactly what won't appear in docs or specs. A surprise that led to a fix belongs here with full context. A surprise that was benign still belongs here so the next agent doesn't have to rediscover it.
5. What we'd do differently
Architectural or process choices that hindsight would change. Distinct from pain points: pain points are about what slowed you down; this is about what you'd redesign. Include the original reasoning so the retro doesn't just say "we were wrong" — say why the original choice looked correct and what new information changed it.
6. Net assessment
Verdict on whether the stated goals were achieved. Required for engineering epics (which have an explicit hypothesis). Optional for phases without a specific hypothesis. One paragraph. Don't hedge — say whether it worked.
7. Follow-up
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 · 53 lines · 60 tokens per session scan A 318719622ef3
soa-write-retrospective is a skill published in the GitHub repository cesarnml/son-of-anton (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 720 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.