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/conventions-checknpx skills add vthinkdeveloper/vthink-agent-toolkit --skill conventions-checkgit 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.00064 | $0.01324 |
| Opus 5 | $0.00032 | $0.00662 |
| Sonnet 5 | $0.00013 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
conventions-check 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Conventions Checker
Overview
This skill checks code changes against the conventions established in the project's own codebase. Rather than enforcing a fixed ruleset, it discovers conventions by examining the project's configuration files, documentation, and existing code patterns — then validates changes against those conventions.
It works in two modes:
- PR mode: Pass a PR number to analyze all changed files in a pull request
- File mode: Pass file paths or glob patterns to check specific files
Workflow
Step 1: Detect Input Mode and Gather Files
Determine if $ARGUMENTS is a PR number (digits only) or file path(s).
If PR number (digits only):
- Use Bash to run:
gh pr diff <number> --name-onlyto get the list of changed files - Use Bash to run:
gh pr diff <number>to get the full diff for context - Read each changed file in full using the Read tool
If file path(s) or glob pattern(s):
- Use Glob to expand any patterns and collect the list of files to check
- Read each file's contents using the Read tool
Step 2: Discover Project Conventions
Before checking anything, learn what conventions this specific project follows. Read these sources in order of priority (skip any that don't exist):
CLAUDE.md(project root) — Often contains explicit architecture, patterns, and coding conventions- Linter/formatter configs — Search for and read:
.eslintrc,.eslintrc.js,.eslintrc.json,.eslintrc.yml.prettierrc,prettier.config.jscheckstyle.xml,.editorconfigtslint.json,biome.jsonpom.xml(for Java plugin configs like compiler version, encoding)package.json(foreslintConfig,prettierfields, and scripts likelint)
- Existing code patterns — For each file type being checked, read 2-3 existing files of the same type in the same directory or nearby directories to identify:
- Naming conventions (classes, methods, files, variables)
- Import ordering and style
- Annotation/decorator usage patterns
- Error handling patterns
- Test structure and assertion style
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 · 121 lines · 64 tokens per session scan A 010f9fbde41f
conventions-check is a skill published in the GitHub repository vthinkdeveloper/vthink-agent-toolkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,324 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…