DBHub is a lightweight Model Context Protocol server that lets compatible AI clients connect to and explore PostgreSQL, MySQL, MariaDB, SQL Server, and SQLite databases through one interface. Developers and other users employ it for schema inspection, query validation, debugging, and controlled read-only database access; the catalogue entries provide agent skills, instructions, an MCP configuration, and a plugin.
Borrowing it
Nothing to install: this file belongs to bytebase/dbhub. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bytebase/dbhub/main/.claude/skills/fix-bug/SKILL.mdgit clone --depth 1 https://github.com/bytebase/dbhubWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bytebase/dbhub/fix-bug)<a href="https://agentmods.dev/skills/bytebase/dbhub/fix-bug"><img src="https://agentmods.dev/badge/skills/bytebase/dbhub/fix-bug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bytebase/dbhub/fix-bug"><img src="https://agentmods.dev/badge/skills/bytebase/dbhub/fix-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00034 | $0.01461 |
| Opus 5.5 | $0.00014 | $0.00584 |
| Sonnet 5.5 | $0.00007 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
fix-bug 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- fix-bug — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bug from GitHub Issue
Systematic workflow for turning a GitHub issue into a working fix in the DBHub codebase.
Workflow
- Fetch → 2. Analyze → 3. Locate → 4. Reproduce → 5. Plan → 6. Implement → 7. Verify → 8. PR
Step 1: Fetch Issue
# From URL: https://github.com/owner/repo/issues/123
gh issue view 123 --json title,body,labels,comments,state
# From another repo
gh issue view 123 --repo owner/repo --json title,body,labels,comments,state
| Input | How to fetch |
|---|---|
https://github.com/owner/repo/issues/42 |
gh issue view 42 --repo owner/repo |
#42 or 42 |
gh issue view 42 (current repo) |
owner/repo#42 |
gh issue view 42 --repo owner/repo |
Step 2: Analyze Issue
Extract from the issue:
- What's broken: Expected vs actual behavior
- Reproduction steps: How to trigger the bug
- Environment: Database type, connection method (DSN, SSH tunnel, TOML config), transport (stdio/HTTP)
- Labels/comments: May reveal affected area or prior investigation
- Linked PRs/issues: Check for related context
Step 3: Locate Relevant Code
Use the issue details to identify which part of the codebase is affected. DBHub has a clear modular structure — most bugs fall into one of these areas:
| Bug Category | Where to Look | Key Files |
|---|---|---|
| Connection failures | Connector implementations | src/connectors/{db-type}/index.ts, src/connectors/manager.ts |
| SQL execution errors | Tool handlers | src/tools/execute-sql.ts, src/utils/allowed-keywords.ts |
| Schema/table listing | Search tool | src/tools/search-objects.ts |
| DSN parsing issues | Parser logic | src/connectors/{db-type}/index.ts (DSNParser), src/utils/dsn-obfuscate.ts, src/utils/safe-url.ts |
| SSH tunnel problems | Tunnel utilities | src/utils/ssh-tunnel.ts, src/utils/ssh-config-parser.ts |
| TOML config issues | Config loading | src/config/toml-loader.ts, src/types/config.ts |
| Multi-database routing | Manager & tools | src/connectors/manager.ts, src/utils/tool-handler-helpers.ts |
| Custom tool issues | Custom handler | src/tools/custom-tool-handler.ts, src/tools/registry.ts |
| HTTP transport | Server setup | src/server.ts |
| Read-only violations | SQL validation | src/utils/allowed-keywords.ts, src/utils/sql-parser.ts |
| Row limiting | SQL rewriting | src/utils/sql-row-limiter.ts |
| API endpoint issues | API handlers | src/api/sources.ts, src/api/requests.ts |
| AWS IAM auth | Token signing | src/utils/aws-rds-signer.ts |
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.
- 2mo ago First seen · 149 lines · 34 tokens per session scan A 4386ea2e874f
fix-bug is a skill published in the GitHub repository bytebase/dbhub (3,753 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,461 once invoked, about $0.0001 per session on Opus 5.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
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
muse_db
Inspect database-backed Muse records for diagnosis and cross-table tracing when purpose-built product tools do not expose the needed state.
ssh-manager
How to use the MCP SSH Manager core tools (sshlistservers, sshexecute, sshupload, sshdownload, sshsync) without breaking a server: server names, the remote shell, time limits and long commands, file transfer pitfalls, security modes, host keys. Use it whenever a task runs a command or moves a file on a remote machine…
ssh-incident
A diagnosis order for "the server is down", "the site is slow", "something broke". Use when investigating a problem on a remote server through the ssh tools, before changing anything.
solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
optimize
Analyze and suggest performance improvements for code, queries, or systems.