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.aftercodegit 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.00025 | $0.01144 |
| Opus 5 | $0.00013 | $0.00572 |
| Sonnet 5 | $0.00005 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
speckit.aftercode 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Outline
This command orchestrates the code delivery pipeline, executing the skilltypesync, changelog, commit, and prgenerate phases in a strict, sequential, and non-interactive flow. It ensures that the entire process, from synchronizing skill type resources to preparing the PR body, is automated while maintaining the precise behavior of each individual step.
Execution is strictly sequential. No steps will be skipped or run in parallel.
Phase 1: Sync Skill Type Resources (/speckit.skilltypesync)
- Action: Initiates the delivery pipeline by invoking
/speckit.skilltypesync. - Process:
- Detects whether this feature includes user-facing config/API/type changes.
- If required, synchronizes skill reference assets under:
skills/vchart-development-assistant/references/type-meta/skills/vchart-development-assistant/references/type-details/
- Runs consistency checks to prevent broken type references in the skill resources.
- Any parameters provided in
$ARGUMENTSwill be passed through (for example:--base,--force,--types).
- Handoff: Upon successful completion, automatically triggers the
changelogphase. - Output Report:
- "Phase 1 (Skill Type Sync) completed."
SYNC_TRIGGER: [auto-detected | forced]UPDATED_TYPE_META: [List of updated files or empty]UPDATED_TYPE_DETAILS: [List of updated files or empty]
Phase 2: Generate Changelog (/speckit.changelog)
- Action: Triggered automatically after
skilltypesynccompletes. - Process:
- Collects commits since a base branch (defaulting to
develop). - Infers the version bump type (
patch,minor,major) automatically from commit messages unless an explicitbumpTypeis passed in$ARGUMENTS. - Generates the necessary change files within the
common/changes/directory. - Any parameters provided in
$ARGUMENTSwill be passed through to override default behavior.
- Collects commits since a base branch (defaulting to
- Handoff: Upon successful completion, automatically triggers the
commitphase. - Output Report:
- "Phase 2 (Changelog) completed."
CREATED_FILES: [List of paths to generated files incommon/changes/]VALIDATION: "Changelog message conforms to Conventional Commits standards."
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.
- 3d ago First seen · 81 lines · 25 tokens per session scan A 8539c623c1a3
speckit.aftercode is a command published in the GitHub repository VisActor/VChart (1,834 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 1,144 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
ship
Commit all changes, push branch, create/update PR, and run local validation.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
pr
End-to-end workflow: verify code, check docs, commit, push, create PR. Run this after implementation is done and tests pass locally.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.