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/yorrick/agent-skillsWrote 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/plugins/yorrick/agent-skills/supabase-security)<a href="https://agentmods.dev/plugins/yorrick/agent-skills/supabase-security"><img src="https://agentmods.dev/badge/plugins/yorrick/agent-skills/supabase-security/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/plugins/yorrick/agent-skills/supabase-security"><img src="https://agentmods.dev/badge/plugins/yorrick/agent-skills/supabase-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
supabase-security 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 21d 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
{
"name": "supabase-security",
"description": "Access-control rules for Supabase projects exposed directly to a browser via PostgREST. Covers the three enforcement layers (GRANT, RLS, triggers), the traps that cause privilege escalation, and how anon keys, JWTs and service_role actually differ.",
"version": "0.1.3",
"author": {
"name": "Yorrick Jansen"
},
"repository": "https://github.com/yorrick/agent-skills",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 205 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 21d ago Changed 3ea666c070b7
- 1mo ago First seen · 11 lines scan A ef937826bce3
supabase-security is a plugin published in the GitHub repository yorrick/agent-skills (11 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
butterbase-skills
Build full-stack apps with Butterbase — AI-Native Backend-as-a-Service. Skills for app creation, schema design, frontend deployment, RLS debugging, serverless functions, and contributing.
migrate-tool
Generate database migrations and code migration scripts for framework upgrades.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
cloud-sql-sqlserver
Connect to Cloud SQL for SQL Server.
sql-database-pipeline
Build SQL database pipelines with dlt: connect to any SQL source, load tables to a destination, tune performance with backends.
materialize
Materialize agent skills: docs, dbt, Terraform, mz-deploy, health checks, freshness debugging, memory tuning, and live demo data.