scope-control

scope-control is a skill for Claude Code, Codex from EvoClaw/amplify. It costs 28 tokens per session (587 once invoked), scanned A, original, MIT.

A scope-management check for research or software projects that detects when planned work is growing beyond a focused, manageable size.

In plain words
What is it for?
Use it to count contributions, assess expanding experiment plans, identify split storylines, and decide what to keep or defer.
Why use it?
It makes scope growth visible and requires an explicit decision before adding major work, helping avoid scattered results and exceeded budgets.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to count contributions, assess expanding experiment plans, identify split storylines, and decide what to keep or defer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/evoclaw/amplify/scope-control
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 EvoClaw/amplify --skill scope-control
Clone the repo
git clone --depth 1 https://github.com/EvoClaw/amplify

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-control

README.md
[![agentmods](https://agentmods.dev/badge/skills/evoclaw/amplify/scope-control/github.svg)](https://agentmods.dev/skills/evoclaw/amplify/scope-control)
Your own site
<a href="https://agentmods.dev/skills/evoclaw/amplify/scope-control"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/scope-control/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 scope-control

Your own site · 80×15
<a href="https://agentmods.dev/skills/evoclaw/amplify/scope-control"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/scope-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 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.00028 $0.00587
Opus 5.5 $0.00011 $0.00235
Sonnet 5.5 $0.00006 $0.00117
Haiku 4.5 $0.00003 $0.00059

Measured 1mo ago against content hash a74d8333f04a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scope-control 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 1mo 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.

skills/scope-control/SKILL.md · 74 lines

How it starts

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

Scope Control (Meta-Control Layer)

Overview

A focused paper with 1–2 strong contributions beats a scattered paper with 5 weak ones. This skill can trigger at ANY phase when scope expansion is detected.

Core principle: Focus is a feature. Scope creep is a bug.

Violating the letter of this rule is violating the spirit of this rule.

Trigger Conditions

Any ONE of these activates this skill:

  • Contribution points or innovation claims exceed 2
  • Experiment matrix is exploding (too many method × dataset × setting combinations)
  • Story line is splitting into unrelated threads
  • Time or resource budget is being exceeded
  • User adds "one more thing" that substantially changes project scope

The Mandatory Response

When triggered, the agent MUST execute all four steps in order:

1. WARN:     "Current scope may be too large for [target venue] as a single paper."
2. QUANTIFY: "Current experiment plan requires ~X GPU-hours. Budget is Y. Excess: Z%."
             or "There are N contribution points. A focused paper typically has 1-2."
3. PROPOSE:  Reduction options, prioritized:
             a) Core contribution to keep
             b) Items to defer to future work
             c) Items to cut entirely
4. PRESENT:  User decides. Agent cannot decide scope reduction on its own.

Skip any step = scope creep enabled = paper quality at risk

Rules

  • The agent proposes reductions but never executes them without user approval.
  • Deferred items go into an explicit "future work" log — they are not forgotten, just prioritized out.
  • After user decides, update the plan and re-verify scope is within bounds.

Red Flags — STOP

  • Adding a third major contribution
  • Experiment table exceeding one page
  • Story line requiring two separate introductions
  • "Just one more baseline" appearing more than twice
  • Resource estimate exceeding budget by more than 30%

Rationalization Prevention

Excuse Reality
"We can fit it all in" Page limits exist. Reviewers penalize unfocused papers.
"Each piece is small" Small pieces compound into confusion.
"We already did the work" Sunk cost. Extra work that dilutes the paper hurts more than helps.
"The reviewer might ask for it" Anticipate reviewers, but don't preemptively answer every possible question.

Read the full file on GitHub · 74 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. 1mo ago First seen · 74 lines · 28 tokens per session scan A a74d8333f04a

Subscribe to this mod's changes

scope-control is a skill published in the GitHub repository EvoClaw/amplify (11 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 587 once invoked, about $0.0001 per session on Opus 5.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-08-30.