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/marcusjellinghaus/mcp-tools-sql/implementation_reviewnpx skills add MarcusJellinghaus/mcp-tools-sql --skill implementation_reviewgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sqlWhat 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.00008 | $0.00351 |
| Opus 5 | $0.00004 | $0.00176 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
implementation_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.
This is a copy
97% identical to implementation_review — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Implementation Review (Code Review)
First, ensure we're up to date:
Call mcp__mcp-workspace__git with command "fetch" and args ["origin"].
Use mcp__mcp-workspace__git with command "status" to check working directory state.
Call mcp__mcp-workspace__check_branch_status.
Confirm and display the current feature branch name.
Then run the code review:
Code Review Request
Use mcp__mcp-workspace__git with command "diff" to get the changes to review.
No need to run all checks; do not use pylint warnings. Feel free to further analyse any mentioned files and/or the file structure.
Focus Areas:
- Logic errors or bugs
- Tests for
__main__functions should be removed (not needed) - Unnecessary debug code or print statements
- Code that could break existing functionality
- Compliance with existing architecture principles, see
docs/architecture/architecture.md
Output Format:
- Summary - What changed (1-2 sentences)
- Critical Issues - Must fix before merging
- Suggestions - Nice to have improvements
- Good - What works well
Do not perform any action. Just present the code review.
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 · 45 lines · 8 tokens per session scan A f2eaaa39eb8c
implementation_review is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 5d ago), licensed MIT. It adds 8 tokens to every session and 351 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to implementation_review, differing in 3 lines, and is treated as a copy.
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…