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/hamsurang/kit/skill-reviewnpx skills add hamsurang/kit --skill skill-reviewgit clone --depth 1 https://github.com/hamsurang/kitWhat 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.00553 |
| Opus 5 | $0.00032 | $0.00277 |
| Sonnet 5 | $0.00013 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
skill-review 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
Skill Review
Reviews a SKILL.md against established best practices and outputs a structured pass/fail report with prioritized recommendations.
Contents
Locating the Target Skill
With explicit path: Use the provided path directly (supports both SKILL.md files and plugin directories).
Without path — search in this order:
- Current directory:
./SKILL.md - Plugin skill dirs:
./plugins/*/skills/*/SKILL.md - Prompt the user if multiple matches found
Review Workflow
- Read
SKILL.mdand any files inreferences/that it links to - Run each check in
references/checklist.md— assign PASS ✅, WARNING ⚠️, or ERROR ❌ - Output the structured report below
Be educational, not just a linter — include a brief explanation of why each finding matters.
Output Format
## Skill Review: [skill-name]
### Summary
**Status:** PASS / NEEDS WORK / FAIL
**Score:** N/N checks passed | N warnings | N errors
### ✅ Passed (N)
- [Check description]
- ...
### ⚠️ Warnings (N)
- **[Check name]**: [finding] — [brief explanation of why it matters]
- ...
### ❌ Errors (N)
- **[Check name]**: [finding] — [why it must be fixed before publishing]
- ...
### 📋 Prioritized Recommendations
1. [Most critical fix first]
2. ...
Severity Definitions
| Severity | Meaning |
|---|---|
| ❌ Error | Violates a spec requirement. Must fix before publishing. |
| ⚠️ Warning | Best practice violation. Should fix for quality. |
| ✅ Pass | Meets the standard. |
Full Rubric
See references/checklist.md for all checks organized by category (frontmatter, description quality, naming, content, structure, scripts, plugin manifest).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 77 lines · 64 tokens per session scan A 8ac2025266e0
skill-review is a skill published in the GitHub repository hamsurang/kit (19 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 553 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-30.
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.