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/concise)<a href="https://agentmods.dev/commands/tinesoft/spec-kit-token-budget/concise"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/concise/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/concise"><img src="https://agentmods.dev/badge/commands/tinesoft/spec-kit-token-budget/concise.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.00071 | $0.01838 |
| Opus 5.5 | $0.00028 | $0.00735 |
| Sonnet 5.5 | $0.00014 | $0.00368 |
| Haiku 4.5 | $0.00007 | $0.00184 |
Grade A, and why
concise 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/speckit.token-budget.concise
The user has invoked /speckit.token-budget.concise with arguments: $ARGUMENTS.
Your task
Manage the concise-output directive in the project's agent memory
file. This directive tells the AI agent — when it next runs any
/speckit.* command — to suppress narrative padding (recap of what it's
about to do, "Let me ...", "I'll go ahead and ...", "Here is what I
did", "I hope this helps") and return only the artifact diff, the file
write, or the structured result.
Output prose is a small share of total session tokens (the input side dominates), but the savings compound across the 4–6 SDD steps and the follow-up clarifications a feature usually needs. More importantly, concise mode shortens turn round-trips, which is the dimension users notice most.
Arguments
on→ enable concise mode (write the directive)off→ disable concise mode (remove the directive)status(or empty) → report current state and which memory file is in use--file=<path>→ force a specific memory file instead of auto-detecting
Algorithm
Step 1 — Locate the memory file
Apply this resolution order. Stop at the first match.
1a. Honor --file=<path> if the user passed one. Skip the rest.
1b. Auto-detect the active spec-kit agent. Look at the project to see which agent's command directory exists and is populated. Common signals, checked in this order:
| Signal | Implies agent | Canonical memory file |
|---|---|---|
.claude/commands/ has files |
Claude Code | CLAUDE.md |
.gemini/commands/ has files |
Gemini CLI | GEMINI.md |
.github/prompts/ has files |
Copilot | .github/copilot-instructions.md |
.cursor/commands/ or .cursor/skills/ has files |
Cursor | .cursor/rules/token-budget.mdc |
.windsurf/workflows/ has files |
Windsurf | .windsurf/rules/token-budget.md |
.tabnine/agent/commands/ has files |
Tabnine | .tabnine/AGENTS.md |
.agents/skills/speckit-*/ has files |
Codex | AGENTS.md |
.pi/prompts/ has files |
Pi Coding Agent | .pi/AGENTS.md |
.kilocode/ has files |
Kilo Code | .kilocode/rules.md |
.roo/ has files |
Roo Code | .roo/rules/token-budget.md |
.clinerules exists |
Cline | .clinerules |
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 · 173 lines · 71 tokens per session scan A 15e179afeeef
concise is a command published in the GitHub repository tinesoft/spec-kit-token-budget (8 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 1,838 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-devsetup
Command description: Analyze the repo and recommend local development setup. Argument hint: [optional specific environment constraints or preferences] Command category: environment Prerequisites: none.
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-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-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.
sddp-clarify
Command description: Reduce ambiguity in the current feature specification. Argument hint: [optional: ambiguity focus or feature directory] Command category: feature-delivery Prerequisites: spec.