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 CodePhobiia/claude-roblox-game-studio --skill retrospectivegit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studioWrote 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/codephobiia/claude-roblox-game-studio/retrospective)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/retrospective"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/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/codephobiia/claude-roblox-game-studio/retrospective"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/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.00022 | $0.00541 |
| Opus 5 | $0.00011 | $0.00270 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
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 9d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retrospective — Sprint Retrospective
Delegate to: producer
Steps
1. Identify Sprint
Ask: "Which sprint are we retrospecting?"
- Default: most recent sprint in
production/sprints/
2. Load Sprint Data
Read:
- Sprint plan (original commitments)
- Milestone reviews (if this sprint spanned a milestone)
- Decision log entries from this sprint's timeframe
- Any bug reports filed
- Metrics if available (agent log, time tracking)
3. Facilitate Reflection
Ask the user to reflect on:
What went well?
- Features shipped as planned
- Good process moments
- Effective collaboration
- Technical wins
What didn't go well?
- Tasks that slipped
- Unexpected blockers
- Process friction
- Bugs that escaped to production
What should we try?
- New practices to experiment with
- Changes to existing process
- Tool improvements
- Agent delegation patterns that might help
What should we stop?
- Practices that aren't paying off
- Meetings or overhead that's not useful
- Tool usage that's hurting flow
4. Extract Action Items
For each "try" or "stop":
- Make it concrete and assignable
- Give it a target sprint
- Define success criteria
5. Generate Retro Document
# Retrospective: Sprint [N]
**Date**: YYYY-MM-DD
**Duration**: [start date] to [end date]
**Participants**: [user]
## Sprint Summary
- Committed: X tasks
- Completed: Y tasks
- Added mid-sprint: Z tasks
- Carried over: W tasks
## What Went Well 🟢
1. [Specific win]
2. [Specific win]
## What Didn't Go Well 🔴
1. [Specific issue]
2. [Specific issue]
## What to Try 🆕
1. [Concrete experiment]
2. [Concrete experiment]
## What to Stop 🛑
1. [Practice to drop]
## Action Items
- [ ] [Action item with owner and target sprint]
- [ ] [Action item with owner and target sprint]
## Key Learnings
- [Insight worth remembering]
- [Insight worth remembering]
Output
Present the retro draft. On approval, save to production/sprints/sprint-<N>-retro.md.
Update production/decision-log.md with key learnings.
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.
- 9d ago First seen · 97 lines · 22 tokens per session scan A 54b980105010
retrospective is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 541 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.