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 skills/vthinkdeveloper/vthink-agent-toolkit/shipnpx skills add vthinkdeveloper/vthink-agent-toolkit --skill shipgit clone --depth 1 https://github.com/vthinkdeveloper/vthink-agent-toolkitWhat 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.00046 | $0.01239 |
| Opus 5 | $0.00023 | $0.00620 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
ship 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship — Conventions Check + Commit + Push
Overview
This skill is your pre-commit quality gate + shipping workflow. It checks staged files against project conventions, generates a good commit message, commits, and pushes — all in one step.
Workflow
Step 1: Pre-flight Checks
- Run
git statusto see the current state - Run
git diff --cached --name-onlyto get the list of staged files - If no staged files:
- Run
git diff --name-onlyto check for unstaged changes - If unstaged changes exist, show them and ask the user which files to stage using AskUserQuestion
- If no changes at all, tell the user "Nothing to ship — working tree is clean" and stop
- Run
- Run
git rev-parse --abbrev-ref HEADto get the current branch name - Display the staged files to the user
Step 2: Conventions Check on Staged Files
Run a conventions check on the staged files only. This is a lightweight version focused on the files being committed.
2a. Discover project conventions:
Read these sources (skip any that don't exist):
CLAUDE.mdin the project root — explicit architecture, patterns, coding conventions- Linter/formatter configs —
.eslintrc*,.prettierrc*,checkstyle.xml,.editorconfig,pom.xml - For each staged file, read 1-2 existing files of the same type in the same directory to identify local patterns
2b. Analyze staged files:
For each staged file:
- Read the file's full contents
- Run
git diff --cached -- <file>to see what specifically changed - Check the changed lines against applicable conventions
- Focus on the diff — don't flag pre-existing issues in unchanged lines
2c. Report findings:
Present a concise report:
## Pre-commit Conventions Check
**Files:** <count> staged files checked
**Result:** <error-count> errors, <warning-count> warnings, <info-count> info
### Findings (if any)
| File | Severity | Rule | Line(s) | Finding | Fix |
|------|----------|------|---------|---------|-----|
| ... | Error | ... | ... | ... | ... |
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 · 132 lines · 46 tokens per session scan A d5ee7d4395b3
ship is a skill published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,239 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.