Skip to content
TrustedSkillsbeta
Back to all skills

Supabase Pentest

Checked
yoanbernabeu·vlatest·database

Identifies potential SQL injection, authentication bypass, and data exposure vulnerabilities within Supabase databases.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-pentest -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

yoanbernabeu

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned yoanbernabeu/supabase-pentest-skills at 0f9612276b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0f9612276b
Manifest
skills/orchestration/supabase-pentest/SKILL.md
Scanned
1 file, 412 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to perform automated penetration testing directly within Supabase projects. It leverages the database's built-in security features and infrastructure to simulate attacks, identify vulnerabilities, and validate access controls without requiring external tools.

When to use it

  • You need to verify that row-level security (RLS) policies are correctly configured before deploying to production.
  • You want to audit your Supabase project for common misconfigurations in a single automated workflow.
  • You require a repeatable method to test how your database responds to simulated malicious queries.
  • You are validating the effectiveness of your current security setup after applying recent patches or policy changes.

Key capabilities

  • Executes comprehensive penetration tests tailored specifically for Supabase environments.
  • Analyzes database schemas, connection strings, and authentication flows for weaknesses.
  • Generates detailed reports highlighting discovered vulnerabilities and potential attack vectors.
  • Operates entirely within the Supabase ecosystem using its native APIs and CLI tools.

Example prompts

  • "Run a full penetration test on my Supabase project to check for exposed tables and weak RLS policies."
  • "Simulate an SQL injection attack against my database connection to see how it handles malformed queries."
  • "Audit the current security configuration of this Supabase instance and list any high-risk findings."

Tips & gotchas

Ensure you have write access to the target Supabase project, as some tests may require temporary modifications to verify fixes. Always run these scans in a staging environment first; automated penetration testing can inadvertently trigger rate limits or alter data if not properly scoped.