VChart is a cross-platform charting library for building data visualizations and annotated, animated storytelling charts. Developers use it across desktop, mobile web, and several mini-program environments through its core and framework-specific packages. The catalogue entries support work with this charting project.
Borrowing it
Nothing to install: this file belongs to VisActor/VChart. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/VisActor/VChart/develop/.cursor/commands/speckit.aftercode.mdgit 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.aftercode)<a href="https://agentmods.dev/commands/visactor/vchart/speckit.aftercode"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.aftercode/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/visactor/vchart/speckit.aftercode"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.aftercode.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.00025 | $0.01144 |
| Opus 5.5 | $0.00010 | $0.00458 |
| Sonnet 5.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 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 — 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.
- 1mo 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,850 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,144 once invoked, about $0.0001 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-30.
Other commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
changelog
Gera changelogs a partir do histórico git e valida commits convencionais. Uso: /changelog [opções].
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.