Borrowing it
Nothing to install: this file belongs to agentdecksdk/agentdeck. 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/agentdecksdk/agentdeck/dev/.claude/skills/milestone-retro/SKILL.mdgit clone --depth 1 https://github.com/agentdecksdk/agentdeckWrote 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/agentdecksdk/agentdeck/milestone-retro)<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/milestone-retro"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/milestone-retro/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/agentdecksdk/agentdeck/milestone-retro"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/milestone-retro.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.00000 | $0.01221 |
| Opus 5.5 | $0.00000 | $0.00488 |
| Sonnet 5.5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
milestone-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 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone retro
Judge the machinery: the gates, the guards, the two agents, the shape of the PRs. Not the product. Whether the features were right is a different question with a different audience.
Every claim in a retro is a number with a query behind it. An opinion about the harness that nobody measured is how the harness got this way.
Setup
The milestone is the set of PRs merged to dev between two tags, or the PRs closing one milestone's issues. Fix that set first and write it down; every phase below is scoped to it.
gh pr list --state merged --limit 200 --json number,title,mergedAt,additions,deletions,changedFiles \
--jq '.[] | select(.mergedAt > "<start>") | "\(.number)\t\(.mergedAt)\t+\(.additions)/-\(.deletions)\t\(.changedFiles)f\t\(.title)"'
Where scripts/agent_scorecard.py has already recorded a PR, read its record instead of recomputing. This skill covers what the scorecard cannot: the gates, the guards, and judgment.
Phases
Work in order. Copy this checklist into your own response and check off each phase:
Retro progress:
- [ ] 1. Gates: which CI checks fired, which never did (references/queries.md)
- [ ] 2. Guards: what the slop rules actually caught (references/queries.md)
- [ ] 3. Agents: dev and reviewer, measured (references/queries.md)
- [ ] 4. PRs: bodies, commits, comment routing (references/queries.md)
- [ ] 5. Criteria: audit the scorecards themselves (references/judging.md)
- [ ] 6. Verdict: file the issues (references/judging.md)
| phase | asks | output |
|---|---|---|
| 1. Gates | Which required checks failed, and what did each catch? A gate that never fails and a gate that always fails are both broken. | a table: gate, runs, failures |
| 2. Guards | Did any mechanical guard catch a defect this milestone, or only formatting? Compare against the findings filed. | guard hits against real findings |
| 3. Agents | Dev: defect at first review, rework ratio, scope creep. Reviewer: escapes, rounds, loop rounds, words per finding. | two scorecards, never merged into one |
| 4. PRs | Body size against the cap, commit hygiene, whether findings were answered in threads or by growing the body. | per-PR table |
| 5. Criteria | Are the scorecards measuring the right things? Which metric changed a decision, which rewards the artifact rather than the value, which can be gamed, which cost is unmeasured. The criteria are under review here, not the agents. | metrics kept, killed, added |
| 6. Verdict | What cost us time, ranked. Each gets an issue or it did not matter. | filed issues |
What ships with it
2 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.
- 2mo ago First seen · 67 lines · 0 tokens per session scan A 77a26fd5ef03
milestone-retro is a skill published in the GitHub repository agentdecksdk/agentdeck (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,221 tokens. 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
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
project-access
Map, suggest and request the folder access a project needs: map (read-only report), suggest (draft .pi/access.json from this project's grants), provision (submit it for line-by-line operator approval). Use on "what folders can this project reach", "set up folder access", "write .pi/access.json", repeated folder access…
goga-task-by-specifying
Interactive task formulation from a raw request.
board
Use this when the person wants a kanban, to-do or status board: cards that move between named columns.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…