Supabase Audit Rpc
CheckedHelps with Supabase, auditing as part of working with databases and data persistence workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add yoanbernabeu/supabase-pentest-skills --skill supabase-audit-rpc -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto 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.
Automated safety checks
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
- Scanned
- 1 file, 399 lines
About this skill
The supabase-audit-rpc skill enables AI agents to execute Remote Procedure Calls (RPCs) within Supabase projects for security auditing. It allows agents to interact directly with database functions to verify access controls, test data integrity, and simulate attack vectors in a controlled environment.
When to use it
- Validating Row Level Security (RLS) policies by attempting unauthorized data access via RPC endpoints.
- Simulating external API threats to ensure Supabase functions handle malicious inputs safely.
- Auditing database function permissions to confirm only authorized roles can trigger specific logic.
- Testing the resilience of custom business logic implemented as Supabase functions against edge cases.
Key capabilities
- Direct execution of RPC calls against Supabase projects.
- Verification of access control mechanisms through simulated user contexts.
- Assessment of input validation within database functions.
- Integration with automated security testing workflows for continuous auditing.
Example prompts
- "Run an audit on my Supabase project to check if the
publicrole can bypass RLS policies on theuserstable via RPC." - "Execute a test RPC call to the
calculate_taxfunction with invalid JSON input to see how it handles errors." - "Audit the permissions of the
update_inventoryRPC to ensure only service roles have write access."
Tips & gotchas
Ensure your Supabase project has the necessary API keys exposed to the AI agent, as direct RPC execution requires authentication. This skill is designed for security testing; use it responsibly and only on environments where you have explicit permission to perform audits.