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/freepeak/ktme/code-reviewnpx skills add FreePeak/ktme --skill code-reviewgit clone --depth 1 https://github.com/FreePeak/ktmeWhat 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.00020 | $0.02879 |
| Opus 5 | $0.00010 | $0.01439 |
| Sonnet 5 | $0.00004 | $0.00576 |
| Haiku 4.5 | $0.00002 | $0.00288 |
Grade A, and why
code-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 3d 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
A systematic approach to reviewing code changes with focus on quality, security, performance, and maintainability.
When to Use
Use this skill when:
- Reviewing pull requests
- Evaluating proposed changes
- Conducting pre-commit reviews
- Performing security audits
- Analyzing code for refactoring opportunities
Review Framework
Phase 1: Understand Context
Goal: Understand what changed and why
Steps:
- Read PR description or commit message
- Identify related issues/tickets
- Understand the business requirement
- Note the scope of changes
Context Checklist:
CONTEXT:
- Issue/PR: [link or number]
- Author: [who made the changes]
- Scope: [files/directories affected]
- Purpose: [what problem it solves]
- Dependencies: [any related PRs or changes]
Questions to Answer:
- What problem does this solve?
- Is this the right approach?
- Are there alternative solutions?
- What's the impact on existing code?
Phase 2: Review the Diff
Goal: Examine actual code changes
Steps:
- Review files changed (start with most important)
- Check for unexpected changes
- Examine each diff hunk carefully
- Note questions and concerns
Diff Review Template:
## Files Changed
### Critical Files
- `file1:line` - [concern or observation]
- `file2:line` - [concern or observation]
### Supporting Files
- `file3:line` - [concern or observation]
### Test Files
- `test_file:line` - [concern or observation]
## Observations
1. [observation with file:line reference]
2. [observation with file:line reference]
Phase 3: Quality Checks
Categories to Evaluate:
3.1 Correctness
CORRECTNESS:
- [ ] Logic is correct
- [ ] Handles edge cases
- [ ] Error handling is appropriate
- [ ] No off-by-one errors
- [ ] Null/None handling is proper
- [ ] Type conversions are safe
ISSUES:
- `file:line` - [description of issue]
3.2 Security
SECURITY:
- [ ] No SQL injection vulnerabilities
- [ ] Input validation is proper
- [ ] No hardcoded secrets
- [ ] Authentication/authorization checked
- [ ] No XSS vulnerabilities (if web)
- [ ] Sensitive data is protected
- [ ] Rate limiting considered
- [ ] Dependencies are safe
ISSUES:
- `file:line` - [description of security concern]
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.
- 3d ago First seen · 503 lines · 20 tokens per session scan A 1b66558d12a6
code-review is a skill published in the GitHub repository FreePeak/ktme (15 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 2,879 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-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.
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…