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/implement_directnpx skills add MarcusJellinghaus/mcp-tools-sql --skill implement_directgit 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.00002 | $0.00631 |
| Opus 5 | $0.00001 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
implement-direct 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 implement-direct — 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Direct
Implement a small, well-defined issue directly — no planning phase, no task tracker.
Resolve Issue Number
The user may provide an issue number as the argument (available as $ARGUMENTS).
If no issue number is provided:
- Read
.vscodeclaude_status.txtand extract the issue number from theIssue #NNNline - If the file doesn't exist or has no issue number, ask the user
Steps
-
Fetch issue details Call
mcp__mcp-workspace__github_issue_viewwith the issue number. Read the issue title, description, and acceptance criteria carefully. -
Checkout/create issue branch
mcp-coder gh-tool checkout-issue-branch <issue_number> -
Understand context
- Read relevant source files referenced in the issue
- Understand the existing code patterns and conventions
- Identify the minimal set of changes needed
-
Implement changes
- Make the required code changes directly
- Follow existing code patterns and conventions
- Keep changes focused and minimal — only what the issue requires
-
Run quality checks
mcp__mcp-tools-py__run_pylint_check— fix all issuesmcp__mcp-tools-py__run_pytest_check(withextra_args: ["-n", "auto"]) — fix all failuresmcp__mcp-tools-py__run_mypy_check— fix all issues./tools/ruff_check.sh— fix all issues
-
Format code Use
mcp__mcp-tools-py__run_format_codeto format all code (black + isort). -
Update issue status
mcp-coder gh-tool set-status status-07:code-review -
Suggest follow-up steps
/commit_push— commit and push changes/check_branch_status— verify branch is clean/implementation_review— request a review of the implementation
Scope Guidance
This skill is designed for small, well-defined issues that can be implemented in a single pass. If the issue is complex or involves multiple components, recommend the full workflow instead:
/create_plan— create a detailed implementation plan/implement— implement the plan step by step
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 · 71 lines · 2 tokens per session scan A feb1311c09dd
implement-direct is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 4d ago), licensed MIT. It adds 2 tokens to every session and 631 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 implement-direct, 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.
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.