scope-check

scope-check is a skill for Claude Code, Codex from striderZA/OpenCodeGameStudios. It costs 52 tokens per session (1,077 once invoked), scanned A, a copy of scope-check, MIT.

A scope-review workflow that compares the work currently planned or underway with the original feature, sprint, or milestone plan. Scope means the agreed set of work.

In plain words
What is it for?
Use it to review a feature, sprint, or milestone for unplanned additions and unfinished work.
Why use it?
It reveals when extra work has been added, shows how much the project has grown, and helps decide what to cut.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/striderza/opencodegamestudios/scope-check
Any agent
npx skills add striderZA/OpenCodeGameStudios --skill scope-check
Clone the repo
git clone --depth 1 https://github.com/striderZA/OpenCodeGameStudios

Made for: Claude Code, Codex.

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/striderza/opencodegamestudios/scope-check.svg)](https://agentmods.dev/skills/striderza/opencodegamestudios/scope-check)
Your own site
<a href="https://agentmods.dev/skills/striderza/opencodegamestudios/scope-check"><img src="https://agentmods.dev/badge/skills/striderza/opencodegamestudios/scope-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,077 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod 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 $0.00052 $0.01077
Opus 5 $0.00026 $0.00539
Sonnet 5 $0.00010 $0.00215
Haiku 4.5 $0.00005 $0.00108

Measured yesterday against content hash 37ffd047c2ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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

This is a copy

97% identical to scope-check — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/modules/design/skills/scope-check/SKILL.md · 129 lines

How it starts

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

Scope Check

This skill is read-only — it reports findings but writes no files.

Compares original planned scope against current state to detect, quantify, and triage scope creep.

Argument: $ARGUMENTS[0] — feature name, sprint number, or milestone name.


Phase 1: Find the Original Plan

Locate the baseline scope document for the given argument:

  • Feature name → read design/gdd/[feature].md or matching file in design/
  • Sprint number (e.g., sprint-3) → read production/sprints/sprint-03.md or similar
  • Milestone → read production/milestones/[name].md

If the document is not found, report the missing file and stop. Do not proceed without a baseline to compare against.


Phase 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 (git log --oneline --since=[start-date])
  • Check for TODO/FIXME comments that indicate unfinished scope additions
  • Check active sprint plan if the feature is mid-sprint

Phase 3: Compare Original vs Current Scope

Produce the comparison report:

## 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 | Source | 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]

Read the full file on GitHub · 129 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. yesterday First seen · 129 lines · 52 tokens per session scan A 37ffd047c2ee

Subscribe to this mod's changes

scope-check is a skill published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 24d ago), licensed MIT. It adds 52 tokens to every session and 1,077 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to scope-check, differing in 2 lines, and is treated as a copy.