scope

scope is a command for coding agents from tinesoft/spec-kit-token-budget. It costs 62 tokens per session (1,223 once invoked), scanned A, original, MIT.

A command that creates a focused reading list for the next stage of a specification-driven development workflow. It names the files and sections the agent should read and records the available token budget.

In plain words
What is it for?
Use it before planning, breaking work into tasks, implementing, analysing, or creating a checklist for a feature.
Why use it?
It keeps the agent’s working context focused by identifying necessary material and sections it can skip.

Command

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 commands/tinesoft/spec-kit-token-budget/scope
Clone the repo
git clone --depth 1 https://github.com/tinesoft/spec-kit-token-budget

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/scope.svg)](https://agentmods.dev/commands/tinesoft/spec-kit-token-budget/scope)
Your own site
<a href="https://agentmods.dev/commands/tinesoft/spec-kit-token-budget/scope"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/scope.svg" alt="Measured on agentmods" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00062 $0.01223
Opus 5 $0.00031 $0.00611
Sonnet 5 $0.00012 $0.00245
Haiku 4.5 $0.00006 $0.00122

Measured 3d ago against content hash 76bff46b2e4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/scope.md · 128 lines

How it starts

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

/speckit.token-budget.scope

The user has invoked /speckit.token-budget.scope with arguments: $ARGUMENTS.

Your task

Produce a reading manifest the agent will follow on the next core SDD command. The goal is to load the smallest set of artifact regions that still covers everything the next phase needs to do its job correctly.

This command never modifies artifacts. It only writes one file: specs/<feature>/.token-budget/scope-<phase>.md.

Inputs

  1. Resolve the active feature directory from the current git branch.
  2. Determine the target phase from $ARGUMENTS:
    • explicit: plan | tasks | implement | analyze | checklist
    • empty → infer the next phase from which artifacts already exist (no plan.md → plan; plan.md but no tasks.md → tasks; both → implement).
  3. Load token-budget-config.ymlscope.max_total_tokens and scope.phase_inputs are the relevant keys.

Algorithm

Step 1 — Candidate set

Start from scope.phase_inputs[<phase>] and expand contracts/ to its actual files. Add any file the user named explicitly via --include=<path> (comma-separated) and remove any file the user named via --exclude=<path>.

Step 2 — Prefer compacted

For each candidate, if a compacted version exists (the file does not end in .full.md and a sibling <base>.full.md exists), use the compacted version. Note the savings. If only .full.md exists, suggest the user run /speckit.token-budget.compact first and continue with the full version.

Step 3 — Section pruning

For each artifact, identify sections the target phase actually consumes and mark the rest as "skim". Defaults:

Phase Reads in full Can skim/skip
plan spec.md (FRs, NFRs, user stories, constraints) spec.md "Background", "Out of scope"
tasks plan.md (Constitution Check, Phase 0/1 outcomes), data-model.md, contracts/* plan.md "Progress Tracking", "Complexity Tracking"
implement tasks.md (full), plan.md (file paths only), contracts/* research.md, quickstart.md, spec rationale
analyze spec.md, plan.md, tasks.md (full) research.md, quickstart.md
checklist spec.md (FRs, NFRs) everything else

Read the full file on GitHub · 128 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. 3d ago First seen · 128 lines · 62 tokens per session scan A 76bff46b2e4a

Subscribe to this mod's changes

scope is a command published in the GitHub repository tinesoft/spec-kit-token-budget (7 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,223 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-08-31.