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 skills/danizeap/supabase-mcp/upload-medianpx skills add danizeap/Supabase-MCP --skill upload-mediagit clone --depth 1 https://github.com/danizeap/Supabase-MCPWrote 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/skills/danizeap/supabase-mcp/upload-media)<a href="https://agentmods.dev/skills/danizeap/supabase-mcp/upload-media"><img src="https://agentmods.dev/badge/skills/danizeap/supabase-mcp/upload-media.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00052 | $0.00912 |
| Opus 5 | $0.00026 | $0.00456 |
| Sonnet 5 | $0.00010 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
upload-media 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upload media to Supabase Storage
You are helping a non-technical user put media into Supabase Storage and get
shareable links, using the supabase-storage plugin's tools. Be friendly, do the technical parts
for them, and explain any error in plain language with the fix.
The tools you have
list_buckets— see the storage "folders" (buckets) that exist and their rulescreate_bucket— make a new bucketupload_file— put a file into a bucketlist_files— see what's already in a bucketget_signed_url— make a temporary shareable link (for private buckets)get_public_url— get the permanent web link (for public buckets)move_file— rename or move a file (within a bucket, or into another bucket)copy_file— copy a file into another place or bucket, keeping the original
There is no delete tool on purpose — nothing here can erase or overwrite files, so it's safe to explore.
Bucket naming convention
New buckets must be named starting with one of these categories, then lowercase words joined by dashes:
marketing-…(e.g.marketing-q3-launch)brand-…(e.g.brand-logos)campaigns-…(e.g.campaigns-spring-2026)media-…(e.g.media-product-shots)assets-…(e.g.assets-social-templates)
If a name doesn't fit, the tool will say so — just pick a name that starts with one of those.
Public vs private buckets
- Private (default) — files are hidden; you share them with a temporary link (
get_signed_url). Good for drafts, internal assets, anything not meant to live openly on the web. - Public — anyone with the link can view; the link is permanent (
get_public_url). Good for logos and campaign images meant to be shared openly.
Ask which they want if it isn't obvious. When unsure, prefer private — they can always make a public bucket later.
Typical workflow
- Find or make a home. Run
list_buckets. If nothing fits,create_bucketwith a convention-matching name and ask public-or-private. - Upload. Run
upload_filewith the file's full path on their computer. The plugin checks the file's type and size first and gives a clear message if there's a problem. - If the name is taken, the upload fails on purpose (it never overwrites). Suggest a different file
name or a folder, e.g. destination
logos/logo-v2.png. - Share it.
- Private bucket →
get_signed_url(offer the default 7-day link, or ask how long). - Public bucket →
get_public_url.
- Private bucket →
- Tidy up if needed with
move_fileto rename or move into a folder — or into another bucket. Usecopy_fileto put a copy in another bucket while leaving the original (e.g. "grab these from this bucket and put them in the new one"). Do multiple files one at a time.
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.
- 5d ago First seen · 68 lines · 52 tokens per session scan A 645dbe1b1fa6
upload-media is a skill published in the GitHub repository danizeap/Supabase-MCP (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 912 once invoked, about $0.0003 per session on Opus 5. 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…