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/give-me-a-commit-messagenpx skills add vthinkdeveloper/vthink-agent-toolkit --skill give-me-a-commit-messagegit 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.00054 | $0.00423 |
| Opus 5 | $0.00027 | $0.00211 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
give-me-a-commit-message 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 2d 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
Suggest Commit Message
Analyze the current changes and suggest a commit message. Do NOT commit or push.
Workflow
Step 1: Gather Context
Run these in parallel:
git diff --staged— staged changesgit diff— unstaged changesgit status— overview of modified/new/deleted filesgit branch --show-current— current branch namegit log --oneline -5— recent commits for style reference
Step 2: Extract Ticket ID
From the branch name, extract any ticket ID pattern (e.g., PROJ-1234, FEAT-567, BUG-42).
- Pattern: uppercase letters + hyphen + numbers (e.g.,
[A-Z]+-\d+) - If found, prefix the commit message with it
Step 3: Generate Message
Write a commit message following these rules:
- If a ticket ID was found, format as:
TICKET-ID: Description - Match the style of recent commits in the repo
- First line: concise summary under 72 characters
- If the change is non-trivial, add a blank line then a short body explaining the "why"
- Focus on why the change was made, not what changed (the diff shows that)
Step 4: Output
Present the suggested message like this:
Suggested commit message:
TICKET-ID: Short description of the change
Optional body explaining why, if needed.
Then say: "Copy and use with git commit -m \"...\", or ask me to refine it."
Do NOT run git commit, git add, or git push. Only suggest.
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.
- 2d ago First seen · 51 lines · 54 tokens per session scan A edbe9682757d
give-me-a-commit-message is a skill published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 423 once invoked, about $0.0003 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.