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.
npx agentmods add commands/visactor/vchart/speckit.commitgit clone --depth 1 https://github.com/VisActor/VChartWhat 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 | $0.00026 | $0.01252 |
| Opus 5 | $0.00013 | $0.00626 |
| Sonnet 5 | $0.00005 | $0.00250 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
speckit.commit 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 2d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
-
Pre-flight checks (local-only):
- Treat this command as zero-input by default: if
$ARGUMENTSis empty, it should still be able to run end-to-end. - Verify the current branch name follows the feature convention (e.g.
001-some-feature) so it can be mapped to aspecs/<spec-id>/directory. - Confirm there are staged or unstaged changes in the working tree; if there are no changes, abort without creating a commit.
- Interpret any CLI flags only as behaviour toggles (e.g.
--edit,--no-verify) and not as a manual commit message.
- Treat this command as zero-input by default: if
-
Load spec context from specs/:
- Derive the feature prefix from the current branch name and resolve the matching
specs/<spec-id>/directory using prefix-based lookup (e.g.001-→specs/001-...). - Read
specs/<spec-id>/plan.mdand extract:- The
## Summarysection — first non-empty line for the natural-language summary. - The top-level title (e.g.
Implementation Plan: ...) as a fallback description. - The
### Source Code (repository root)code block, which lists the source layout for this feature.
- The
- Derive the feature prefix from the current branch name and resolve the matching
-
Infer
typefrom Summary keywords:- Build a short text corpus from the Summary sentence and plan title.
- Using only that text, map the commit
typeaccording to the following rules (case-insensitive):- Contains
bugorfix→fix - Contains
refactororrefactoring→refactor - Contains
perforperformance→perf - Contains
docs,doc, ordocumentation→docs - Contains
test,tests, orunit→test - Contains
implement,implementation,add,support, orfeature→feat - Otherwise →
chore
- Contains
- Do not inspect file paths, git history, or
common/changeswhen choosing the type.
-
Infer
scopefrom Source Code paths:- From the
Source Code (repository root)block inplan.md, parse all paths that live underpackages/<name>/.... - Collect the second-level directory names (e.g.
packages/vchart/→vchart,packages/vchart-types/→vchart-types), de-duplicate, and sort. - Build the
scopeas:- A comma-separated list of all such package names when one or more packages are present.
- The literal string
monorepowhen nopackages/*paths can be found.
- Do not attempt to infer scope from other folders or git diffs.
- From the
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.
- 2d ago First seen · 79 lines · 26 tokens per session scan A 5bcd4e557e23
speckit.commit is a command published in the GitHub repository VisActor/VChart (1,834 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 1,252 once invoked, about $0.0001 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-30.
Other commands, from other repositories
guide
Every method on App should have its own unit tests.
lattice-cycle
Run one Lattice work cycle — pull the next runnable tasks, dispatch the agent team, verify, commit, push, and advance the queue.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.