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_new_tasksnpx skills add MarcusJellinghaus/mcp-tools-sql --skill implementation_new_tasksgit 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.00350 |
| Opus 5 | $0.00004 | $0.00175 |
| Sonnet 5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
implementation_new_tasks 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
100% identical to implementation_new_tasks — 0 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
Create Further Implementation Tasks
Append new implementation tasks to the project plan after code review identified areas needing additional work.
Instructions
Please expand the implementation plan stored under pr_info/steps
Update the pr_info/steps/Decisions.md with the decisions we took.
Please create additional self-contained steps (pr_info/steps/step_1.md, pr_info/steps/step_2.md, etc.).
Please update the summary (pr_info/steps/summary.md).
Requirements for the new implementation steps:
- Follow Test-Driven Development where applicable. Each step should have its own test implementation followed by related functionality implementation.
- Each step must include a clear LLM prompt that references the summary and that specific step
- Apply KISS principle - minimize complexity, maximize maintainability
- Keep code changes minimal and follow best practices
Each Step Must Specify:
- WHERE: File paths and module structure
- WHAT: Main functions with signatures
- HOW: Integration points (decorators, imports, etc.)
- ALGORITHM: 5-6 line pseudocode for core logic (if any)
- DATA: Return values and data structures
Please also update the task tracker (pr_info/TASK_TRACKER.md).
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 · 37 lines · 8 tokens per session scan A 9ce99017adad
implementation_new_tasks 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 350 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to implementation_new_tasks, differing in 0 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…