scope-check

scope-check is a skill for Claude Code from HolyMonkey/youtube-example-ai-studio. It costs 32 tokens per session (763 once invoked), scanned A, a copy of scope-check, MIT.

A scope review that compares a feature, sprint, or milestone's original plan with what is currently being built.

In plain words
What is it for?
Use it to list scope changes, estimate their effort, identify who added them, and decide what should be cut.
Why use it?
It identifies additions, dropped work, and unfinished scope before the project grows beyond its original limits.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to list scope changes, estimate their effort, identify who added them, and decide what should be cut.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-studio/scope-check.svg)](https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/scope-check)
Your own site
<a href="https://agentmods.dev/skills/holymonkey/youtube-example-ai-studio/scope-check"><img src="https://agentmods.dev/badge/skills/holymonkey/youtube-example-ai-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 100% 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.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

This is a copy

100% identical to scope-check — 0 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.

.claude/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 HolyMonkey/youtube-example-ai-studio (11 stars, last pushed 5mo 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. It is 100% identical to scope-check, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens