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_approvenpx skills add MarcusJellinghaus/mcp-tools-sql --skill implementation_approvegit 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.00009 | $0.00266 |
| Opus 5 | $0.00005 | $0.00133 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
implementation_approve 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
89% identical to implementation_approve — 5 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
Approve Implementation
Approve the implementation and transition the issue to PR-ready state.
Instructions:
-
Run branch-status check: Call
mcp__mcp-workspace__check_branch_status. -
If
branch-statusreports a base branch other thanmain, ask the user to confirm this is intentional before proceeding. -
Only if the branch-status check passes, run the set-status command and confirm it succeeded:
mcp-coder gh-tool set-status status-08:ready-pr
Note: If the branch-status check fails, report the failures to the user and do not set the label. If the set-status command fails, report the error to the user. Do not use --force unless explicitly asked.
Effect: Changes issue status from status-07:code-review to status-08:ready-pr.
- After the label is set, call
mcp__mcp-workspace__check_branch_statusagain to verify CI and PR status.
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 · 29 lines · 9 tokens per session scan A 863bd1268d23
implementation_approve is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 266 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to implementation_approve, differing in 5 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.
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.