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/ttcc666/databasemcpserver/database-mcp-clinpx skills add ttcc666/DatabaseMcpServer --skill database-mcp-cligit clone --depth 1 https://github.com/ttcc666/DatabaseMcpServerWhat 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.00177 | $0.01837 |
| Opus 5 | $0.00088 | $0.00919 |
| Sonnet 5 | $0.00035 | $0.00367 |
| Haiku 4.5 | $0.00018 | $0.00184 |
Grade A, and why
database-mcp-cli 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DatabaseMcpServer CLI
Operate DatabaseMcpServer from the shell safely, deterministically, and with evidence.
Scope Gate
- Use this skill for direct CLI invocations:
tool,config,init, or-web. - Do not use CLI instructions to answer “how do I connect Claude/Cursor/Cline over MCP stdio?” Treat that as client integration.
- Identify which executable is under test:
- Installed global tool:
DatabaseMcpServer - Current repository source:
dotnet run --project 'src\DatabaseMcpServer\DatabaseMcpServer.csproj' -f 'net9.0' -- ...
- Installed global tool:
- Never assume the installed tool contains a source-tree change. If a new tool exists in source but global CLI says “unknown tool”, compare source help with
dotnet tool list --global.
Core Workflow
-
Discover exact syntax before guessing:
DatabaseMcpServer tool list DatabaseMcpServer tool help <tool_name> DatabaseMcpServer config help <subcommand> -
Resolve the executable version and config path.
-
Establish the current connection with
get_current_database; do not infer it fromisDefault. -
Run read-only checks before SQL or writes:
validate_configuration → test_connection → get_database_config → list_databases. -
Inspect schema before composing SQL:
is_any_table → get_table_schema/get_column_infos_by_table_name. -
Execute writes only within the user-authorized scope and with
--yes. -
Capture argv, exit code, stdout, stderr, classification, and cleanup.
Version and Source Truth
-
Check an installed version with:
dotnet tool list --global | Select-String databasemcpserver -
DatabaseMcpServer --versionis unsupported and exits2; do not recommend it as a working check. -
When validating a repository change, prefer
dotnet run ... -- tool help <name>or the freshly packed local tool. State explicitly whether evidence came from source or the installed global tool. -
If the global tool is stale, upgrade or install a newly versioned local package before diagnosing the feature as missing.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 147 lines · 177 tokens per session scan A 1c9b7e9aecd4
database-mcp-cli is a skill published in the GitHub repository ttcc666/DatabaseMcpServer (37 stars, last pushed 27d ago), licensed MIT. It adds 177 tokens to every session and 1,837 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.