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.prcreate.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.prcreate)<a href="https://agentmods.dev/commands/visactor/vchart/speckit.prcreate"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.prcreate/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.prcreate"><img src="https://agentmods.dev/badge/commands/visactor/vchart/speckit.prcreate.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.00017 | $0.00338 |
| Opus 5.5 | $0.00007 | $0.00135 |
| Sonnet 5.5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
speckit.prcreate 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.
What it actually says
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
-
Check Inputs:
- Title: The Pull Request title (Required).
- Head Branch: Source branch (defaults to current branch:
git branch --show-current). - Base Branch: Target branch (defaults to
develop). - Body File: Path to PR body content (defaults to
.trae/output/pr.body.local.md).
-
Verify Environment:
- Check if
ghCLI is installed:gh --version. - Check authentication status:
gh auth status. - Note: Explicitly ignore
GITHUB_TOKENenv var to force browser-based auth if needed.
- Check if
-
Execute PR Creation:
- Construct and run the
gh pr createcommand:gh pr create --title "<TITLE>" --body-file "<BODY_FILE>" --base "<BASE>" --head "<HEAD>" --web - Note: The
--webflag is optional but recommended if the user wants to review in browser before final submission, otherwise remove it to create directly. Based on user preference or default to direct creation if not specified.
- Construct and run the
-
Report Output:
- Capture the command output.
- Display the URL of the newly created Pull Request.
- Verify the URL is valid.
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 · 37 lines · 17 tokens per session scan A 4a34e0a10499
speckit.prcreate is a command published in the GitHub repository VisActor/VChart (1,850 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 338 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.