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/lifedever/skills-plugin/image-uploadnpx skills add lifedever/skills-plugin --skill image-uploadgit clone --depth 1 https://github.com/lifedever/skills-pluginWrote 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/lifedever/skills-plugin/image-upload)<a href="https://agentmods.dev/skills/lifedever/skills-plugin/image-upload"><img src="https://agentmods.dev/badge/skills/lifedever/skills-plugin/image-upload.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 | $0.00117 | $0.00957 |
| Opus 5 | $0.00059 | $0.00478 |
| Sonnet 5 | $0.00023 | $0.00191 |
| Haiku 4.5 | $0.00012 | $0.00096 |
Grade A, and why
image-upload 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
image-upload
Upload any image to your own GitHub repo and get back three URL formats — jsDelivr CDN (fast, public), GitHub raw, and Markdown — ready to paste into documentation, blog posts, or chats.
Prerequisites (one-time setup)
- A GitHub repo for images. Create one yourself (public preferred so jsDelivr CDN serves it), e.g.
your-username/images. ghCLI installed and authenticated:brew install gh gh auth loginjqinstalled (for JSON serialization):brew install jqpngpaste(only for clipboard screenshot mode):brew install pngpaste- Set environment variables in your shell profile (
~/.zshrcor~/.bashrc):
Reload your shell orexport IMAGE_HOST_REPO="your-username/images" # required export IMAGE_HOST_BRANCH="master" # optional, default: master export IMAGE_HOST_BASE_DIR="uploads" # optional, default: uploadssource ~/.zshrc.
Per-invocation overrides via --repo, --branch, --base-dir flags also work.
Usage
Upload one or more files:
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" path/to/image.png
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" file1.jpg file2.png file3.webp
Upload from clipboard (most recent screenshot, or files copied in Finder):
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" --clipboard
Auto-copy a specific URL format to system clipboard:
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" --copy markdown file.png
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" --copy jsdelivr --clipboard
bash "${CLAUDE_SKILL_DIR}/scripts/upload_image.sh" --copy raw file1.jpg file2.jpg
--copy values: jsdelivr (CDN), raw (GitHub raw), markdown ( format).
How it works
- Files are renamed to timestamp format:
20260513-143025.jpg. Batch uploads add an index:-1,-2, etc. - Each image is committed to
<base-dir>/YYYY/MM/<name>.<ext>in your repo. - Filename conflicts auto-resolve with a numeric suffix.
- Multiple files upload in parallel (with retry on transient 409s from branch HEAD races).
- For each image, three URLs are printed: jsDelivr CDN, GitHub raw, and Markdown.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 95 lines · 117 tokens per session scan A 4a98afab2269
image-upload is a skill published in the GitHub repository lifedever/skills-plugin (11 stars, last pushed 13d ago), licensed MIT. It adds 117 tokens to every session and 957 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…