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.
git clone --depth 1 https://github.com/tinesoft/spec-kit-token-budgetWrote 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/commands/tinesoft/spec-kit-token-budget/scope)<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/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/commands/tinesoft/spec-kit-token-budget/scope"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/scope.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.00062 | $0.01223 |
| Opus 5.5 | $0.00025 | $0.00489 |
| Sonnet 5.5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
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 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.
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
- Resolve the active feature directory from the current git branch.
- 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).
- explicit:
- Load
token-budget-config.yml—scope.max_total_tokensandscope.phase_inputsare 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 |
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.
- 1mo ago First seen · 128 lines · 62 tokens per session scan A 76bff46b2e4a
scope is a command published in the GitHub repository tinesoft/spec-kit-token-budget (8 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,223 once invoked, about $0.0002 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-31.
Other commands, from other repositories
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-plan
Command description: Create an implementation plan from the current feature specification. Argument hint: [optional: planning constraints or focus areas] Command category: feature-delivery Prerequisites: spec.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
sddp-specify
Command description: Create a feature specification from a feature description. Argument hint: [feature description] Command category: feature-delivery Prerequisites: project-instructions.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.