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 skills add sso-ss/vibe-ship-it --skill upload-filegit clone --depth 1 https://github.com/sso-ss/vibe-ship-itWrote 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/sso-ss/vibe-ship-it/upload-file)<a href="https://agentmods.dev/skills/sso-ss/vibe-ship-it/upload-file"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/upload-file/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/skills/sso-ss/vibe-ship-it/upload-file"><img src="https://agentmods.dev/badge/skills/sso-ss/vibe-ship-it/upload-file.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.01598 |
| Opus 5.5 | $0.00025 | $0.00639 |
| Sonnet 5.5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
upload-file 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 2mo 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upload File
Lets users upload images or files. Stores them in the cloud, displays them on the site.
Default: Supabase Storage
Already using Supabase for data, so storage is built in.
Step 1: Create Storage Bucket
Via Supabase dashboard:
"Go to Supabase dashboard → Storage → New Bucket. Name it something like 'images' or 'uploads'. Set it to Public if these images should be visible on your site."
Or via SQL:
insert into storage.buckets (id, name, public)
values ('images', 'images', true);
-- Allow anyone to upload (for public forms)
create policy "Anyone can upload" on storage.objects
for insert with check (bucket_id = 'images');
-- Allow anyone to view (for public images)
create policy "Anyone can view" on storage.objects
for select using (bucket_id = 'images');
Step 2: Create Upload Component
'use client'
import { createClient } from '@/utils/supabase/client'
import { useState } from 'react'
export function ImageUpload({ onUpload }: { onUpload: (url: string) => void }) {
const [uploading, setUploading] = useState(false)
async function handleUpload(e: React.ChangeEvent<HTMLInputElement>) {
const file = e.target.files?.[0]
if (!file) return
setUploading(true)
const supabase = createClient()
// Generate unique filename
const fileExt = file.name.split('.').pop()
const fileName = `${Date.now()}-${Math.random().toString(36).slice(2)}.${fileExt}`
const { error } = await supabase.storage
.from('images')
.upload(fileName, file)
if (error) {
alert('Upload failed. Try again.')
setUploading(false)
return
}
// Get the public URL
const { data: { publicUrl } } = supabase.storage
.from('images')
.getPublicUrl(fileName)
onUpload(publicUrl)
setUploading(false)
}
return (
<label className="block cursor-pointer">
<div className="border-2 border-dashed border-gray-300 rounded-xl p-8 text-center hover:border-gray-400 transition-colors">
{uploading ? (
<p className="text-gray-500">Uploading...</p>
) : (
<>
<p className="text-gray-500">Click to upload an image</p>
<p className="text-sm text-gray-400 mt-1">PNG, JPG, WebP up to 5MB</p>
</>
)}
</div>
<input
type="file"
accept="image/*"
onChange={handleUpload}
className="hidden"
disabled={uploading}
/>
</label>
)
}
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.
- 2mo ago First seen · 218 lines · 63 tokens per session scan A a0c531a66b8c
upload-file is a skill published in the GitHub repository sso-ss/vibe-ship-it (12 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 1,598 once invoked, about $0.0003 per session on Opus 5.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-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…