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/compact)<a href="https://agentmods.dev/commands/tinesoft/spec-kit-token-budget/compact"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/compact/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/compact"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/compact.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.00065 | $0.02187 |
| Opus 5.5 | $0.00026 | $0.00875 |
| Sonnet 5.5 | $0.00013 | $0.00437 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade A, and why
compact 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/speckit.token-budget.compact
The user has invoked /speckit.token-budget.compact with arguments: $ARGUMENTS.
Your task
Compact one or more SDD artifacts in the active feature so that downstream spec-kit commands consume fewer tokens, without losing any requirement, decision, contract, ID, user story, or acceptance criterion.
Inputs
-
Resolve the active feature directory (typically
specs/<NNN-feature-name>/) from the current git branch using the existing spec-kit conventions. If the user is not on a feature branch, ask which feature to operate on and stop. -
Parse
$ARGUMENTS:- empty → compact every artifact in the active feature directory.
spec|plan|tasks|research|data-model|contracts|quickstart|constitution→ compact only that one (or that group, in the case ofcontracts). When the target isconstitution, compact bothspecs/<feature>/constitution.md(if it exists in the active feature) and.specify/memory/constitution.md(if it exists at the project root). Either may be absent; skip silently if so.- a relative or absolute path → compact that file.
--level=light|medium|aggressive→ override the configured level for this run only.--dry-run→ report what would change, write nothing.
-
Load
token-budget-config.ymlfrom the extension directory if present, otherwise use the template defaults. The keys you care about are:compact.level,compact.preserve_sections,compact.drop_sections,compact.preserve_code_blocks,compact.preserve_id_patterns,compact.keep_full_backup.
Algorithm — apply in order, per artifact
Step 1 — Backup
If keep_full_backup is true and <artifact>.full.md does not yet exist,
copy the current artifact to <artifact>.full.md. Never overwrite an
existing backup. The backup is the source of truth for re-compaction at a
different level later.
Step 1b — Guard injection (skipped for --dry-run)
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 · 202 lines · 65 tokens per session scan A 2b9c66ea6fe3
compact is a command published in the GitHub repository tinesoft/spec-kit-token-budget (8 stars, last pushed 3mo ago), licensed MIT. It adds 65 tokens to every session and 2,187 once invoked, about $0.0003 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.