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/sakhilchawla/skillkit/reviewnpx skills add sakhilchawla/skillkit --skill reviewgit clone --depth 1 https://github.com/sakhilchawla/skillkitWrote 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/skills/sakhilchawla/skillkit/review)<a href="https://agentmods.dev/skills/sakhilchawla/skillkit/review"><img src="https://agentmods.dev/badge/skills/sakhilchawla/skillkit/review.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00432 |
| Opus 5 | $0.00008 | $0.00216 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
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 5d 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
Code Review
Review the current branch's changes against the base branch (default: main).
Phase 1: Gather Context
- Determine the base branch: use $ARGUMENTS if provided, otherwise detect main/master
- Run
git diff <base>...HEAD --statto see changed files - Run
git diff <base>...HEADto see the full diff - Read any modified files in full for surrounding context
Phase 2: Critical Review (MUST complete first)
Check for issues that would block merging. For each finding, cite the file and line.
Security: SQL injection, XSS, command injection, hardcoded secrets, unsafe deserialization Correctness: Logic errors, null access, race conditions, missing error handling Data Loss: Destructive operations without confirmation, missing transactions Breaking Changes: Public API changes, removed exports, changed behavior
Phase 3: Suggestions Review
Performance: N+1 queries, unnecessary re-renders, missing memoization Maintainability: Dead code, duplicated logic, complex functions, missing types Testing: Untested critical paths, brittle assertions, missing edge cases
Output Format
## Critical Issues (must fix before merge)
- [CRITICAL] <file>:<line> — <description>
## Warnings (should fix)
- [WARNING] <file>:<line> — <description>
## Suggestions (consider)
- [SUGGESTION] <file>:<line> — <description>
## Summary
<1-2 sentence overall assessment>
Rules
- Never approve code with Critical issues
- Be specific: cite file, line, and the problematic code
- Suggest fixes, not just problems
- If the diff is clean, say so — do not invent issues
What ships with it
2 files 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.
- 5d ago First seen · 57 lines · 16 tokens per session scan A 36968f3dec3f
review is a skill published in the GitHub repository sakhilchawla/skillkit (6 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 432 once invoked, about $0.0001 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…