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 milestone-reviewgit 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/milestone-review)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/milestone-review"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/milestone-review/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/milestone-review"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/milestone-review.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.00559 |
| Opus 5 | $0.00011 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
milestone-review 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 11d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/milestone-review — Milestone Completion Review
Delegate to: producer
Steps
1. Identify Milestone
Ask: "Which milestone are we reviewing?"
- Default: Most recent milestone in
production/milestones/
2. Load Milestone Criteria
Read the milestone document. Extract:
- Success criteria
- Deliverables
- Dependencies
- Risk register
- Definition of done
3. Verify Each Criterion
For each criterion, check:
- Design docs: Exist and reviewed? (delegate to
game-designerfor verification) - Implementation: Complete and reviewed? (delegate to
lead-programmer) - Tests: Written and passing? (delegate to
qa-tester) - Security: No critical findings? (delegate to
exploit-security-specialist) - Performance: Benchmarks met? (delegate to
performance-analyst) - Polish: Rough edges addressed?
4. Generate Status Report
# Milestone Review: [Milestone Name]
**Status**: [Complete / Incomplete / At Risk]
**Date**: YYYY-MM-DD
**Reviewer**: [user name]
## Criteria Status
| Criterion | Status | Notes |
|-----------|--------|-------|
| Feature X implemented | ✅ Done | |
| Feature Y implemented | ⚠️ Partial | UI incomplete |
| No critical security findings | ✅ Done | |
| Performance benchmarks | ❌ Missed | Server frame time 45ms (target 33ms) |
## Deliverables
- [x] GDD for combat system
- [x] Implementation of combat core
- [ ] Polish pass
- [x] Unit tests
- [ ] Exploit check
## Risk Status
- Risk 1: [description] — Mitigated
- Risk 2: [description] — Still open, impact Medium
## Recommendation
[ ] **Advance to next milestone**
[X] **Not ready — blockers listed below**
### Blockers
1. Performance regression in combat system (server frame time)
2. Combat UI 40% incomplete
3. No exploit check run yet
### Next Steps
1. Delegate perf issue to `performance-analyst`
2. Finish UI via `ui-programmer`
3. Run `/exploit-check` before re-review
Output
Present the report. On approval, save to production/milestones/milestone-<name>-review.md.
Update production/session-state/ with milestone status.
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.
- 11d ago First seen · 78 lines · 22 tokens per session scan A 11384e729754
milestone-review 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 559 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-08-31.
Other skills, from other repositories
gate-check
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.
setup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
day-one-patch
Prepare a day-one patch for a game launch. Scopes, prioritises, implements, and QA-gates a focused patch addressing known issues discovered after gold master but before or immediately after public launch. Treats the patch as a mini-sprint with its own QA gate and rollback plan.
launch-checklist
Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.
milestone-review
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.