scope-check

scope-check is a skill for Claude Code, OpenCode from TraftG/opencode-game-studio. It costs 32 tokens per session (763 once invoked), scanned A, original, MIT.

A scope review that compares a feature, sprint, or milestone's original plan with the work currently implemented or underway.

In plain words
What is it for?
Use it to inspect design documents, code, commits, and unfinished tasks, then list scope additions, removals, effort, and impact.
Why use it?
It reveals work that was added or dropped, helping teams see scope creep and decide what to keep or cut.

Skill for Claude CodeOpenCode

Written for Claude Code and OpenCode: allowed-tools in frontmatter, but also installed under .opencode/.

Good fit Use it to inspect design documents, code, commits, and unfinished tasks, then list scope additions, removals, effort, and impact.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/traftg/opencode-game-studio/scope-check
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 TraftG/opencode-game-studio --skill scope-check
Clone the repo
git clone --depth 1 https://github.com/TraftG/opencode-game-studio

Made for: Claude Code, OpenCode.

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 scope-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/traftg/opencode-game-studio/scope-check.svg)](https://agentmods.dev/skills/traftg/opencode-game-studio/scope-check)
Your own site
<a href="https://agentmods.dev/skills/traftg/opencode-game-studio/scope-check"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/scope-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 763 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.00032 $0.00763
Opus 5 $0.00016 $0.00381
Sonnet 5 $0.00006 $0.00153
Haiku 4.5 $0.00003 $0.00076

Measured 3d ago against content hash a8ee43a21bcc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

scope-check 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 3d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.opencode/skills/scope-check/SKILL.md · 74 lines

What it actually says

When this skill is invoked:

  1. Read the original plan — Find the relevant document:

    • If a feature name: read the design doc from design/gdd/
    • If a sprint number: read the sprint plan from production/sprints/
    • If a milestone: read the milestone definition from production/milestones/
  2. Read the current state — Check what has actually been implemented or is in progress:

    • Scan the codebase for files related to the feature/sprint
    • Read git log for commits related to this work
    • Check for TODO comments that indicate unfinished scope additions
  3. Compare original vs current scope:

    ## Scope Check: [Feature/Sprint Name]
    Generated: [Date]
    
    ### Original Scope
    [List of items from the original plan]
    
    ### Current Scope
    [List of items currently implemented or in progress]
    
    ### Scope Additions (not in original plan)
    | Addition | Who Added | When | Justified? | Effort |
    |----------|-----------|------|------------|--------|
    | [item] | [commit/person] | [date] | [Yes/No/Unclear] | [S/M/L] |
    
    ### Scope Removals (in original but dropped)
    | Removed Item | Reason | Impact |
    |-------------|--------|--------|
    | [item] | [why removed] | [what's affected] |
    
    ### Bloat Score
    - Original items: [N]
    - Current items: [N]
    - Items added: [N] (+[X]%)
    - Items removed: [N]
    - Net scope change: [+/-N] ([X]%)
    
    ### Risk Assessment
    - **Schedule Risk**: [Low/Medium/High] — [explanation]
    - **Quality Risk**: [Low/Medium/High] — [explanation]
    - **Integration Risk**: [Low/Medium/High] — [explanation]
    
    ### Recommendations
    1. **Cut**: [Items that should be removed to stay on schedule]
    2. **Defer**: [Items that can move to a future sprint/version]
    3. **Keep**: [Additions that are genuinely necessary]
    4. **Flag**: [Items that need a decision from producer/creative-director]
    
  4. Output the scope check with a clear verdict:

    • On Track: Scope within 10% of original
    • Minor Creep: 10-25% scope increase — manageable with adjustments
    • Significant Creep: 25-50% scope increase — need to cut or extend timeline
    • Out of Control: >50% scope increase — stop and re-plan

Rules

  • Scope creep is additions without corresponding cuts or timeline extensions
  • Not all additions are bad — some are discovered requirements. But they must be acknowledged and accounted for.
  • When recommending cuts, prioritize preserving the core player experience over nice-to-haves
  • Always quantify scope changes — "it feels bigger" is not actionable, "+35% items" is
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. 3d ago First seen · 74 lines · 32 tokens per session scan A a8ee43a21bcc

Subscribe to this mod's changes

scope-check is a skill published in the GitHub repository TraftG/opencode-game-studio (38 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 763 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

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

striderZA/OpenCodeGameStudios · 64 tokens

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.

striderZA/OpenCodeGameStudios · 40 tokens

cgs-sprint-plan

Use for sprint plan tasks that create a 1-2 week sprint plan with goals, tasks, owners, dependencies, risks, and acceptance criteria; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 50 tokens

cgs-sprint-status

Use for sprint status tasks that report sprint progress, blockers, risk changes, completed work, and next decisions; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 42 tokens

cgs-team-combat

Use for team combat tasks that coordinate combat design, implementation, tuning, animation, VFX, audio, and QA handoffs; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 46 tokens

cgs-team-level

Use for team level tasks that coordinate level design, blockout, art, scripting, lighting, optimization, and playtest handoffs; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 46 tokens