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.skilltypesyncgit 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.00029 | $0.00873 |
| Opus 5 | $0.00015 | $0.00436 |
| Sonnet 5 | $0.00006 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
speckit.skilltypesync 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 yesterday.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider user input if provided. Treat it as optional CLI-style overrides only (for example: --base develop, --force, --types ILabelSpec,IData).
Outline
-
Resolve diff scope:
- Default base branch is
develop. - If
$ARGUMENTScontains--base <branch>, use that branch as comparison base. - Collect changed files from:
- staged + unstaged local changes, and
- branch diff against base (
<base>...HEAD).
- De-duplicate all changed paths.
- Default base branch is
-
Determine whether sync is required:
- Mark as requires sync when changes affect user-facing configuration or API/type definitions, including (but not limited to):
packages/vchart/src/typings/**packages/vchart/src/chart/**/interface/**packages/vchart/src/component/**/interface/**packages/vchart/src/series/**/interface/**packages/vchart/src/theme/**- any public API or option schema files referenced by VChart docs.
- If no matching files and no
--force, stop with a clear summary: "No user config/API changes detected, skill type sync skipped."
- Mark as requires sync when changes affect user-facing configuration or API/type definitions, including (but not limited to):
-
Identify impacted type entities:
- From changed TypeScript definitions, extract impacted type/interface names (for example
ILabelSpec,IData,ITheme). - Build two impact sets:
- Meta impact: chart/common entries that need
type-meta/*.jsonupdates. - Detail impact: concrete types needing
type-details/*-Type-Definition.mdupdates.
- Meta impact: chart/common entries that need
- If
$ARGUMENTSincludes--types, merge explicit type names into the detail impact set.
- From changed TypeScript definitions, extract impacted type/interface names (for example
-
Update
type-metaresources:- Target directory:
skills/vchart-development-assistant/references/type-meta/. - For each impacted chart/common meta file:
- sync user-visible property paths,
- sync
requiredflags, - sync
typeandisSimplefields, - remove stale keys that no longer exist in source typings.
- Keep JSON valid and stable (no duplicated keys, deterministic field ordering where possible).
- Target directory:
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.
- yesterday First seen · 77 lines · 29 tokens per session scan A b84ffb26b4f0
speckit.skilltypesync is a command published in the GitHub repository VisActor/VChart (1,834 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 873 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.