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.
git clone --depth 1 https://github.com/lovablelabs/mcpWrote 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/commands/lovablelabs/mcp/db)<a href="https://agentmods.dev/commands/lovablelabs/mcp/db"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/db/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/commands/lovablelabs/mcp/db"><img src="https://agentmods.dev/badge/commands/lovablelabs/mcp/db.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00179 |
| Opus 5.5 | $0.00005 | $0.00072 |
| Sonnet 5.5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
db 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 1mo 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.
What it actually says
Work with a Lovable project's database. Input: $ARGUMENTS
- Resolve the
project_id(uselist_projectsif the user gave a name). - Call
get_database_status. If no database exists and the user wants one, confirm and callenable_database(takes 30–60s; one-time per project). - If the user supplied SQL, run it with
query_database.- ⚠️
query_databasehas full read / write / schema permissions. Show the user the exact SQL and get explicit confirmation before running anything that writes data or alters schema.
- ⚠️
- For connection details (connection string, API URL), call
get_database_connection_info.
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.
- 1mo ago First seen · 13 lines · 13 tokens per session scan A 5be8a27f8d14
db is a command published in the GitHub repository lovablelabs/mcp (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 13 tokens to every session and 179 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 commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
splunk-observability-database-monitoring-setup
Render and validate Splunk Observability Cloud Database Monitoring collector configuration for MongoDB, PostgreSQL, Microsoft SQL Server, MySQL, MariaDB, and Oracle through the Splunk OTel Collector. Keeps secrets out of chat, argv, and rendered files; DB credentials are referenced through Kubernetes Secrets or local…
rls-plan
Supabase RLS + access-control audit + remediation plan — no SQL until approved.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.