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.changeloggit clone --depth 1 https://github.com/VisActor/VChartWrote 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/visactor/vchart/speckit.changelog)<a href="https://agentmods.dev/commands/visactor/vchart/speckit.changelog"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.changelog.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00872 |
| Opus 5 | $0.00017 | $0.00436 |
| Sonnet 5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
speckit.changelog 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
-
Resolve feature spec from branch:
- Treat this command as zero/low-input: if
$ARGUMENTSis empty, infer everything from the current branch andspecsdirectory. - Derive the feature prefix from the current branch name (for example,
001-fix-bug→ prefix001) and locate the matching directory underspecs/whose name starts with that prefix. - From that directory, resolve:
plan.mdas the primary source of truth for the change description.checklists/requirements.mdas an optional, secondary source when the plan lacks a clear summary.
- If no matching
specs/<spec-id>/can be found, return an error instead of guessing.
- Treat this command as zero/low-input: if
-
Extract Summary from specs-only context:
- From
plan.md, read the## Summarysection and take the first non-empty line as the feature summary. - If the
Summarysection is empty or missing, fall back in order to:- The top-level title of
plan.md(for example,Implementation Plan: ...). - A concise line derived from
checklists/requirements.md. - The feature directory name or branch name.
- The top-level title of
- Normalize the final summary to a single line (strip markdown markers, collapse whitespace) without inventing new wording.
- From
-
Infer bump type (spec-driven):
- Default
bumpTypetopatch. - Scan the content of
plan.md(case-insensitive) for explicit markers:- If it contains
BREAKING CHANGEor a clearMAJORmarker → usemajor. - Else if it contains a clear
MINORmarker → useminor. - Else if it only contains
PATCHor no marker at all → keeppatch.
- If it contains
- If the user passes an explicit bump type argument, validate it against
patch | minor | major | noneand override the inferred value.nonemeans "no version bump" while still allowing a change file to be written if Rush supports it.
- Default
-
Construct the Rush change message (no git history):
- Build a single-line message using the spec id and the inferred summary, for example:
update changes for <spec-id>: <summary sentence>
- If the user provided an explicit message argument, prefer that over the inferred one.
- Do not analyze git commit history, file diffs, or
common/changescontents when constructing this message; the only semantic source isspecs/<spec-id>/.
- Build a single-line message using the spec id and the inferred summary, for example:
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.
- 4d ago First seen · 64 lines · 35 tokens per session scan A 0e59a2b2816d
speckit.changelog is a command published in the GitHub repository VisActor/VChart (1,834 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 872 once invoked, about $0.0002 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
review-renovate
Review and merge renovate PRs with automerge configuration updates.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Prepare a release by updating docs and bumping the version.
ship
Deliver the increment. Then go live with a rollback you have run.
release-now
Create a git tag + GitHub Release for open-pr — an official release if standing on main, an RC if standing on a branch with an open PR (a dev tool specific to this repo, not shipped in the plugin).