Database Sentinel

Multi-backend DB security auditor for Supabase and MongoDB (RLS, exposed keys, CVEs)

Tested · Works

Test report

Verdict
Tested · Works
Score
8.4/10
Tested
Jul 17, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · edd3849

Ran its detection sweep and Supabase anti-pattern catalog against a planted project: it correctly identified the backend, flagged the NEXT_PUBLIC_..._SERVICE_ROLE_KEY as CRITICAL (the anon-vs-service_role distinction a naive review misses), the USING(true) policy, and the RLS-off table, each tied to a Splinter lint ID, CVE-2025-48757, and ready fix SQL. Its headline claim, testing whether policies actually prevent access, needs a live database, so that dynamic layer stayed unmeasured. Note the frontmatter advertises Firebase, Postgres and MySQL audits that the body admits are Phase 3-5 not-yet-implemented.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 5/5
  • Triggers reliably 5/5
  • Output vs. baseline 7/10
  • Docs & honesty 4/5

What Database Sentinel does

Audits database backends for misconfigurations: disabled RLS, exposed service-role keys, permissive policies, and known CVEs, with plain-language findings and exact fix SQL. Triggers on phrases like "audit my Supabase", "is my DB exposed", "check my database", or "is my app secure". Supabase and MongoDB backends are implemented; Firebase/Postgres/MySQL are advertised but marked not-yet-implemented.

How to install Database Sentinel

git clone https://github.com/Farenhytee/database-sentinel.git
mkdir -p ~/.claude/skills
cd database-sentinel && cp -r . ~/.claude/skills/database-sentinel

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Database Sentinel

  • /database-sentinel Multi-backend DB security auditor for Supabase and MongoDB (RLS, exposed keys, CVEs)

It also activates on plain-language prompts like these:

  • audit my Supabase project for exposed service-role keys
  • check whether any of my database tables have RLS disabled
  • is my MongoDB backend exposed to any known CVEs right now

Frequently asked questions

Is the Database Sentinel skill free?
Yes. The skill itself is free from Farenhytee/database-sentinel. SkillProof publishes the install command and an independent test verdict at no cost.
Does Database Sentinel work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 17, 2026. Verdict: Tested · Works. Ran its detection sweep and Supabase anti-pattern catalog against a planted project: it correctly identified the backend, flagged the NEXT_PUBLIC_..._SERVICE_ROLE_KEY as CRITICAL (the anon-vs-service_role distinction a naive review misses), the USING(true) policy, and the RLS-off table, each tied to a Splinter lint ID, CVE-2025-48757, and ready fix SQL. Its headline claim, testing whether policies actually prevent access, needs a live database, so that dynamic layer stayed unmeasured. Note the frontmatter advertises Firebase, Postgres and MySQL audits that the body admits are Phase 3-5 not-yet-implemented.
What is the Database Sentinel SkillProof Score?
8.4/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 4/5.
How do I install Database Sentinel?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Database Sentinel with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.