skill-scope-control

skill-scope-control is a skill for Claude Code, Codex from IAPro-Community/Orquestrador-Maestro. It costs 36 tokens per session (636 once invoked), scanned A, original, Apache-2.0.

A review workflow that checks whether code changes, diffs, or pull requests still match the stated goal. A pull request is a proposed set of changes for review before merging.

In plain words
What is it for?
Use it to review a change against its original objective, identify unrelated scope, and suggest whether to retain, split, or justify the extra work.
Why use it?
It helps catch extra work that has slipped into a change and makes it easier to decide whether to keep, separate, or explain it.

Skill for Claude CodeCodex

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

Good fit Use it to review a change against its original objective, identify unrelated scope, and suggest whether to retain, split, or justify the extra work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iapro-community/orquestrador-maestro/skill-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 IAPro-Community/Orquestrador-Maestro --skill skill-scope-control
Clone the repo
git clone --depth 1 https://github.com/IAPro-Community/Orquestrador-Maestro

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-scope-control"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-scope-control.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 636 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00036 $0.00636
Opus 5.5 $0.00014 $0.00254
Sonnet 5.5 $0.00007 $0.00127
Haiku 4.5 $0.00004 $0.00064

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

Security

Grade A, and why

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

codex/skills/skill-scope-control/SKILL.md · 49 lines

How it starts

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

Skill Scope Control

Use quando a conversa indicar que uma mudança pode ter crescido além do objetivo: “essa alteração ficou grande demais”, “o diff saiu do escopo”, “o PR está misturado” ou “o que não deveria estar aqui?”.

Fluxo conversacional

  1. Registre o objetivo em uma frase. Se ele não estiver claro, peça essa frase antes de classificar o diff.
  2. Faça um inventário dos arquivos, subsistemas, dependências e comportamentos alterados.
  3. Classifique cada descoberta com uma categoria canônica: IN_SCOPE, REQUIRED_DEPENDENCY, DISCOVERED_WORK ou OUT_OF_SCOPE.
  4. IN_SCOPE pode ser executado quando atende diretamente um critério de aceitação. REQUIRED_DEPENDENCY só pode ser executado com justificativa, impacto e evidência da necessidade.
  5. Registre DISCOVERED_WORK no mecanismo existente de follow-up/handoff e não o inclua silenciosamente no plano. Bloqueie OUT_OF_SCOPE.
  6. Recomende manter, separar ou justificar explicitamente, sempre apontando a evidência.
  7. Entregue um resumo curto com itens, risco de mistura e próximo passo.

O padrão é somente leitura: não edite, reverta, faça stage, commit ou push. A skill pode ser usada antes ou durante revisão de código, release ou planejamento.

Contenção no autopilot

Para cada descoberta, atualize o task ledger ou handoff existente antes de agir. Somente IN_SCOPE e REQUIRED_DEPENDENCY justificada são elegíveis para execução. Uma tentativa de executar descoberta sem justificativa deve virar bloqueio, não uma autorização implícita.

Ferramenta opcional

Se scripts/scope_creep.py já estiver disponível no projeto, ele pode ser usado para uma análise offline e reproduzível. Não instale nem execute código externo sem autorização. Passe o objetivo e os caminhos de forma segura, sem interpolar texto da conversa em comandos de shell.

Guardrails

  • Keep this skill compact; move long details into references/ and link them from this file.
  • Do not include tokens, local paths, logs, private project names, or stale API examples.
  • Prefer project evidence over generic assumptions.

Read the full file on GitHub · 49 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 Changed · +6 lines 595cec66e8f1
  2. 2mo ago First seen · 43 lines · 36 tokens per session scan A 5db4a2bb1679

Subscribe to this mod's changes

skill-scope-control is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (63 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 636 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.