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/bytebase/dbhub/setupnpx skills add bytebase/dbhub --skill setupgit clone --depth 1 https://github.com/bytebase/dbhubWhat 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.00026 | $0.00714 |
| Opus 5 | $0.00013 | $0.00357 |
| Sonnet 5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
setup 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 yesterday.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DBHub Setup
The database connection string (DSN) is entered in the plugin's configuration dialog and stored in Claude Code's secure storage. This plugin is read-only and caps results at 1000 rows.
Connecting or changing the database
-
Help the user build their DSN if they don't have one:
- PostgreSQL:
postgres://user:password@localhost:5432/dbname - MySQL:
mysql://user:password@localhost:3306/dbname - MariaDB:
mariadb://user:password@localhost:3306/dbname - SQL Server:
sqlserver://user:password@localhost:1433/dbname - SQLite:
sqlite:///absolute/path/to/database.db(no credentials)
Append
?sslmode=requirefor SSL (sslmode=disablefor local databases). URL-encode special characters in the password. Recommend a least-privilege, read-only database account. Full DSN options (SQL Server named instances/NTLM, PostgreSQL cert verification): https://dbhub.ai/installation - PostgreSQL:
-
Point them at the config dialog: run
/plugin, open dbhub → configuration, and set the connection string there. The user should not paste the password into the chat. -
Reconnect: run
/mcpand reconnect thedbhubserver (or restart Claude Code).
Troubleshooting a failing connection
- Test the DSN outside the plugin (redact the password in anything shown in chat):
A JSONecho '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"setup-check","version":"0"}}}' | DBHUB_DSN='<dsn>' npx -y @bytebase/dbhub@latest --transport stdio --config <plugin-root>/dbhub.tomlinitializeresponse means the config parsed and the server started; a connection error points at host/port/credentials/SSL. - Common causes: database unreachable from this machine (host/port, VPN, firewall), wrong
sslmode, un-encoded special characters in the password, a SQLite path that isn't absolute. - If the server dies instantly with
sh: dbhub: command not found, the npx cache entry is corrupted (concurrent npx runs can race during install). Find and remove the entry for@bytebase/dbhubunder~/.npm/_npx/*/package.json, then reconnect — npx will reinstall it cleanly. - Requires Node.js >= 22.5.0 (
node --version).
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.
- yesterday First seen · 44 lines · 26 tokens per session scan A fbaf3af845ec
setup is a skill published in the GitHub repository bytebase/dbhub (3,431 stars, last pushed 11d ago), licensed MIT. It adds 26 tokens to every session and 714 once invoked, about $0.0001 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…