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/issue_updatenpx skills add MarcusJellinghaus/mcp-tools-sql --skill issue_updategit 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.00010 | $0.00490 |
| Opus 5 | $0.00005 | $0.00245 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
issue_update 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
92% identical to issue_update — 12 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
Update GitHub Issue
Based on our prior /issue_analyse discussion, update the GitHub issue with refined content.
Instructions:
-
If no issue context is found from prior analysis, respond: "No issue context found. Please run
/issue_analyse <number>first." -
First, fetch the current issue content: Call
mcp__mcp-workspace__github_issue_viewwith the issue number. -
Draft updated issue text with:
- Clear, concise title
- Well-structured body with implementation ideas
-
Write the issue body to a temp file (avoids bash escaping issues with markdown):
mcp__mcp-workspace__save_file(file_path=".scratch/issue_body_temp.md", content=body_content)
- Update the issue using
--body-file:
gh issue edit <issue_number> --title "NEW_TITLE" --body-file .scratch/issue_body_temp.md
- Clean up the temp file:
mcp__mcp-workspace__delete_this_file(file_path=".scratch/issue_body_temp.md")
Editing Base Branch:
- To add a base branch: Insert
### Base Branchsection with the branch name - To change a base branch: Update the content under the existing section
- To remove a base branch: Delete the entire
### Base Branchsection
The base branch must be a single line. Multiple lines will cause an error during branch creation.
The updated issue should include:
- Summary of the requirement
- Discussed implementation approach (concise)
## Constraints & Rationale— non-obvious gotchas and the "why" behind decisions. Skip if none identified.## Decisionstable — decided topics so/issue_analysewon't re-ask. Skip if none yet.
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 · 56 lines · 10 tokens per session scan A 8dca21fe24a9
issue_update is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 490 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to issue_update, differing in 12 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.