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.
npx agentmods add plugins/supabase/agent-skills/marketplace/plugin marketplace add supabase/agent-skillsgit clone --depth 1 https://github.com/supabase/agent-skillsGrade A, and why
supabase-agent-skills 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 yesterday.
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-agent-skills",
"owner": {
"name": "Supabase",
"email": "[email protected]"
},
"metadata": {
"description": "Official Supabase agent skills for Claude Code",
"version": "1.1.0"
},
"plugins": [
{
"name": "supabase",
"description": "Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).",
"source": "./",
"strict": false,
"skills": ["./skills/supabase"]
},
{
"name": "postgres-best-practices",
"description": "Postgres performance optimization and best practices. Use when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.",
"source": "./",
"strict": false,
"skills": ["./skills/supabase-postgres-best-practices"]
}
]
}
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.
- yesterday First seen · 28 lines scan A 6eaa13f01a50
supabase-agent-skills is a plugin published in the GitHub repository supabase/agent-skills (2,562 stars, last pushed 20d 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-30.
Other plugins, from other repositories
google-plugins
Plugin marketplace listing 17 plugins: alloydb, alloydb-omni, bigtable, cloud-sql-mysql, cloud-sql-postgresql.
xcode-build-skills
A multi-skill plugin for benchmarking and optimizing Xcode builds, compile hotspots, project settings, and Swift Package Manager dependency overhead.
newsjack
Newsjack — PR-operator skills for coding agents.
produck
Plugin marketplace listing 1 plugin: produck.
asset-pipeline
Refine and process generated game assets: animated spritesheets, Aseprite parsing, sprite-sheet pipelines, pixel-grid snapping, and image-to-procedural-Three.js props.
beautiful-mermaid
Render Mermaid diagrams as SVG and PNG using the Beautiful Mermaid library. Use when the user asks to render a Mermaid diagram.