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 cenconq25/claude-code-app-studio --skill scope-checkgit clone --depth 1 https://github.com/cenconq25/claude-code-app-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/cenconq25/claude-code-app-studio/scope-check)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/scope-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/scope-check/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/cenconq25/claude-code-app-studio/scope-check"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/scope-check.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.00054 | $0.01689 |
| Opus 5 | $0.00027 | $0.00844 |
| Sonnet 5 | $0.00011 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
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 5d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Check
Sprints accumulate. A story added Tuesday because "it's quick" plus another Wednesday becomes Friday's overrun. This skill measures the drift from the original plan and surfaces a recommendation.
Read-only. Outputs a snapshot + cut recommendations.
Purpose / When to Run
Run when:
- The team feels overloaded mid-sprint
- A new story is being considered for an in-flight sprint
- Sprint status shows "At risk" and the cause is unclear
- A PM wants to confirm a feature has not silently expanded
Distinct from /sprint-status (current state) — this skill compares planned vs. actual scope.
Inputs
- Mode:
sprint(compare current sprint to its initial plan) orfeature <slug>(compare an epic to its initial scope) - The relevant sprint plan or epic file
- Mid-Sprint Update sections (added by
/sprint-plan update) - All current stories
- The git history if available — but the skill does not require it
Outputs
- Printed snapshot. No file writes.
Phase 1: Resolve Mode
If no argument: ask
- Prompt: "Check sprint scope or feature scope?"
- Options:
Active sprint,Specific feature (free text — epic slug)
Phase 2: Establish Baseline
For sprint mode:
- Read the active sprint plan
- Extract the original Sprint Backlog table (the one written when the plan was first created, before any
## Mid-Sprint Updatesection) - Extract the original sprint goal and Success Looks Like
For feature mode:
- Read the epic's
EPIC.md - Extract the original Story Backlog (Section 13 if it was filled before stories were added; else infer from the original PRD's TR-IDs)
- Extract the original scope from EPIC Section 8 (Out of Scope)
Phase 3: Establish Current
Walk the same backlog now:
- For sprint mode: read the live story files for each story in the plan, plus any added via Mid-Sprint Updates
- For feature mode: list all stories under
production/epics/<slug>/story-*.md
For each story now in scope, classify:
- In original plan — was there from day 1
- Added — appears in a Mid-Sprint Update section, or post-dates the original plan's create date
- Expanded — was in the plan but acceptance criteria have grown (count criteria; if the story file has more than the plan implied, mark as expanded)
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.
- 5d ago First seen · 182 lines · 54 tokens per session scan A a1c656f7febb
scope-check is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,689 once invoked, about $0.0003 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.