project-stage-detect

project-stage-detect is a skill for Claude Code from CodePhobiia/claude-roblox-game-studio. It costs 34 tokens per session (893 once invoked), scanned A, original, MIT.

A project-status assessment that examines code, design documents, assets, tests, production files, and Git history. It uses that information to place a Roblox game in a stage such as pre-production, development, polish, or live.

In plain words
What is it for?
Use it to measure code and documentation coverage, check assets and tests, review production progress, and determine the project's current stage.
Why use it?
It gives a project team a clearer view of what exists and what is missing. This helps avoid treating an early prototype like a finished game, or overlooking gaps before launch.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to measure code and documentation coverage, check assets and tests, review production progress, and determine the project's current stage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codephobiia/claude-roblox-game-studio/project-stage-detect
Install

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.

Any agent
npx skills add CodePhobiia/claude-roblox-game-studio --skill project-stage-detect
Clone the repo
git clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studio

Made for: Claude Code.

Wrote 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.

agentmods badge for project-stage-detect

README.md
[![agentmods](https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/project-stage-detect/github.svg)](https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/project-stage-detect)
Your own site
<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/project-stage-detect"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/project-stage-detect/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.

agentmods 80×15 button for project-stage-detect

Your own site · 80×15
<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/project-stage-detect"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/project-stage-detect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.00893
Opus 5 $0.00017 $0.00447
Sonnet 5 $0.00007 $0.00179
Haiku 4.5 $0.00003 $0.00089

Measured 9d ago against content hash 393ab6ae05d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

project-stage-detect 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.

.claude/skills/project-stage-detect/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/project-stage-detect — Project Stage Analysis

Delegate to: producer (with technical-director for code analysis)

Steps

1. Scan Code

# Count Luau files
find src/ -name "*.lua" -o -name "*.luau" | wc -l

# Count total lines of code
find src/ -name "*.lua" -o -name "*.luau" -exec wc -l {} + | tail -1

# Look for major systems (directories or modules)
ls src/ServerScriptService src/ServerStorage src/ReplicatedStorage 2>/dev/null

2. Scan Design Docs

# Count GDDs
find design/gdd -name "*.md" | wc -l

# Check for master GDD
ls design/gdd/master-gdd.md 2>/dev/null && echo "EXISTS" || echo "MISSING"

# Check for systems index
ls design/gdd/systems-index.md 2>/dev/null && echo "EXISTS" || echo "MISSING"

3. Scan Assets

# Count assets by type
find assets/images -type f 2>/dev/null | wc -l
find assets/audio -type f 2>/dev/null | wc -l
find assets/models -type f 2>/dev/null | wc -l

4. Check Testing

find tests -name "*.spec.lua" -o -name "*.spec.luau" 2>/dev/null | wc -l

5. Check Production Artifacts

ls production/sprints/*.md 2>/dev/null | wc -l
ls production/milestones/*.md 2>/dev/null | wc -l

6. Check Git History

git log --oneline | wc -l  # total commits
git log --since="1 month ago" --oneline | wc -l  # recent activity

7. Classify Stage

Stage Signals
Pre-production No master GDD, <5 GDDs, <1000 LOC, minimal assets
Production Master GDD exists, systems being built, code growing fast, sprints active
Polish All core systems implemented, bug triage focused, perf work happening
Live Published, version tags exist, patch notes history, active retro cadence

8. Identify Gaps

For each stage, identify what's missing:

Pre-production gaps
  • No game concept?
  • No creative pillars?
  • No target audience defined?
Production gaps
  • No systems-index?
  • GDDs without corresponding code?
  • Code without corresponding GDDs?
  • No tests?
  • No CI?

Read the full file on GitHub · 134 lines

Changes

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.

  1. 9d ago First seen · 134 lines · 34 tokens per session scan A 393ab6ae05d7

Subscribe to this mod's changes

project-stage-detect is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 893 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-09-03.

Related

Other skills, from other repositories

gameobject-component-destroy

Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.

IvanMurzak/Unity-MCP · 49 tokens

unity-version-split

Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).

IvanMurzak/Unity-MCP · 59 tokens

godot-signals-groups

Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…

gamedev-skills/awesome-gamedev-agent-skills · 95 tokens

motion

How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.

OpenDCAI/GameFactory-3A · 0 tokens

unity-addressables

Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).

Besty0728/Unity-Skills · 25 tokens

threejs-exposure-color-grading

Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.

scottstts/Threejs-Awesome-Graphics-Agent-Skills · 60 tokens