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 Dokkabei97/forged-claude-code --skill retrospective-guidegit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/retrospective-guide)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/retrospective-guide"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/retrospective-guide.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.00039 | $0.00739 |
| Opus 5 | $0.00019 | $0.00369 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
retrospective-guide 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 7d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective Guide - Sprint Retrospective Templates
Overview
Structured retrospectives that drive real improvement. The goal isn't to vent — it's to commit to one actionable change each sprint.
1. When to Apply
| Trigger | Behavior |
|---|---|
| End of sprint | Retro template generation |
| "retro", "회고" | Interactive format selection |
| Post-incident | Incident-specific retro template |
2. Retro Formats
Keep / Problem / Try (기본)
# Sprint [N] Retrospective — YYYY-MM-DD
## Keep (계속할 것)
- [What worked well and should continue]
## Problem (문제점)
- [What didn't work or caused friction]
## Try (시도할 것)
- [Specific experiments for next sprint]
## Action Items
| Action | Owner | Due | From |
|--------|-------|-----|------|
| [Specific action] | @name | [date] | Problem #1 |
4Ls (Liked, Learned, Lacked, Longed For)
## Liked 👍
- [What the team enjoyed]
## Learned 📚
- [New knowledge or insights gained]
## Lacked 😕
- [What was missing or insufficient]
## Longed For 🌟
- [What the team wishes they had]
Sailboat ⛵
## Wind (추진력) — What pushed us forward?
- [Accelerators]
## Anchor (방해) — What held us back?
- [Blockers and friction]
## Rocks (위험) — What risks lie ahead?
- [Upcoming risks]
## Island (목표) — Where are we heading?
- [Sprint/quarter goal]
3. Facilitation Tips
- Review previous action items first (5 min)
- Silent brainstorming → write sticky notes individually (5 min)
- Group and vote on topics (5 min)
- Discuss top 3 voted items (15 min)
- Commit to 1-3 action items with owners and dates (5 min)
- Total: 30-45 minutes
4. Anti-Patterns
| Anti-Pattern | Fix |
|---|---|
| No action items | Always end with specific, owned actions |
| Same problems every retro | Track action item completion rate |
| Blame-focused | Establish "no blame" ground rule |
| Skipping retros "too busy" | This is how you GET less busy |
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.
- 7d ago First seen · 131 lines · 39 tokens per session scan A 52f001493c6e
retrospective-guide is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 739 once invoked, about $0.0002 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-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
create-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…