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/skills-il/developer-tools/cloudinary-assetsnpx skills add skills-il/developer-tools --skill cloudinary-assetsgit clone --depth 1 https://github.com/skills-il/developer-toolsWhat 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.00124 | $0.05417 |
| Opus 5 | $0.00062 | $0.02708 |
| Sonnet 5 | $0.00025 | $0.01083 |
| Haiku 4.5 | $0.00012 | $0.00542 |
Grade A, and why
cloudinary-assets scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(python:*) Bash(curl:*) WebFetch How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudinary Assets
Instructions
Step 1: Verify Cloudinary Configuration
Check for Cloudinary credentials:
import os
def get_cloudinary_config():
"""Get Cloudinary config from environment."""
# Option 1: CLOUDINARY_URL (preferred)
cloudinary_url = os.environ.get('CLOUDINARY_URL')
if cloudinary_url:
return {"url": cloudinary_url}
# Option 2: Individual variables
cloud_name = os.environ.get('CLOUDINARY_CLOUD_NAME')
api_key = os.environ.get('CLOUDINARY_API_KEY')
api_secret = os.environ.get('CLOUDINARY_API_SECRET')
if all([cloud_name, api_key, api_secret]):
return {"cloud_name": cloud_name, "api_key": api_key, "api_secret": api_secret}
return None # Credentials not configured
If not configured, guide the user:
- Sign up at https://cloudinary.com (free tier: 25 credits per month)
- Find credentials in Dashboard, then Programmable Media, then API Keys
- Set CLOUDINARY_URL=cloudinary://API_KEY:API_SECRET@CLOUD_NAME
Step 2: Choose Operation
| Operation | API | Method | When |
|---|---|---|---|
| Upload image | Upload API | POST /image/upload | New image to store |
| Upload video | Upload API | POST /video/upload | New video to store |
| Transform image | URL-based | GET (URL) | Resize, crop, effects |
| Optimize delivery | URL-based | GET (URL) | Performance improvement |
| List assets | Admin API | GET /resources | Browse media library |
| Delete asset | Upload API | POST /image/destroy | Remove media |
| Get asset details | Admin API | GET /resources/{id} | Check metadata |
Step 3: Upload Media
Upload an image:
import requests
import hashlib
import time
def upload_image(file_path, cloud_name, api_key, api_secret,
folder="", asset_folder="", tags=None):
"""Upload image to Cloudinary."""
timestamp = str(int(time.time()))
# EVERY upload parameter except file, cloud_name, api_key, resource_type
# and signature itself must be in the signed string, sorted alphabetically.
# Signing only a subset (e.g. omitting tags) yields "Invalid Signature".
params = {"timestamp": timestamp}
if folder:
params["folder"] = folder # fixed folder mode
if asset_folder:
params["asset_folder"] = asset_folder # dynamic folder mode (new accounts)
if tags:
params["tags"] = ",".join(tags)
params_to_sign = "&".join(f"{k}={v}" for k, v in sorted(params.items()))
signature = hashlib.sha1(
f"{params_to_sign}{api_secret}".encode()
).hexdigest()
url = f"https://api.cloudinary.com/v1_1/{cloud_name}/image/upload"
data = {"api_key": api_key, "signature": signature, **params}
with open(file_path, "rb") as f:
response = requests.post(url, data=data, files={"file": f}, timeout=(10, 180))
response.raise_for_status()
return response.json()
What ships with it
7 files 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.
- 2d ago First seen · 379 lines · 124 tokens per session scan A 88f7b31328c1
cloudinary-assets is a skill published in the GitHub repository skills-il/developer-tools (10 stars, last pushed 5d ago), licensed MIT. It adds 124 tokens to every session and 5,417 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.