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/djrhails/dotfiles/cdn-uploadnpx skills add DJRHails/dotfiles --skill cdn-uploadgit clone --depth 1 https://github.com/DJRHails/dotfilesWhat 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.00123 | $0.01024 |
| Opus 5 | $0.00062 | $0.00512 |
| Sonnet 5 | $0.00025 | $0.00205 |
| Haiku 4.5 | $0.00012 | $0.00102 |
Grade A, and why
cdn-upload 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 3d 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.
- Verify a URL is live: `curl -s -o /dev/null -w '%{http_code} %{content_type}' "$url"` → `200 image/png`. How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cdn-upload — public URLs for local files via cdn.hails.info
cdn.hails.info is a public Cloudflare R2 bucket (r2:cdn-hails-info). Upload a file and it is
reachable at https://cdn.hails.info/<key>. Because the URL is public, GitHub renders it inline in
markdown even for private repos (where committed/raw.githubusercontent.com image links 404 or
are blocked by the camo proxy).
Use it
~/.agents/skills/cdn-upload/scripts/cdn-upload path/to/figure.png [more.png ...]
# prints one https://cdn.hails.info/img/<sha256[:32]>.png per file on stdout
The script (mirrors DJRHails/kb bin/r2_upload.py):
- Content-addressed: key is
img/<sha256[:32]><ext>, so identical bytes collapse to one object and re-uploads are idempotent (same URL every time). - Immutable cache header on upload (
Cache-Control: public, max-age=31536000, immutable). - Routing: a local
rcloner2:remote if configured; else, inside a gantry worker (thegantryCLI is on PATH and$GANTRY_API_KEYis injected), it runsgantry attach— which POSTs to gantry's/agent/attachments, since gantry holds the R2 creds the sandboxed worker lacks, and returns the samecdn.hails.info/img/<sha>URL (images only); else it scps totrifle(the user's Mac, whererclone+ ther2:remote live) and uploads from there. So it works from a maintainer host, a gantry worker, or any tailnet host.
Embedding in a GitHub PR/issue (the common case)
url=$(.../scripts/cdn-upload figures/foo.png)- Put
in the PR/issue body — the alt text is the file's original repo-relative path (the CDN key is a content hash, so the alt is the only provenance the embed keeps); the human description goes in a bold caption line below the image, not in the alt. - Update an existing PR body with the REST API:
gh api --method PATCH repos/<owner>/<repo>/pulls/<n> -F [email protected]. Prefer this overgh pr edit, which fails closed on any host whose token lacksread:org: aGITHUB_TOKENscopedrepo+workflowonly cannot run the querygh pr editreads the PR with, which carries aTeamrequested-reviewer fragment (organization{login},name,slug) — so it exits 1 and writes nothing even for a body-only edit on a personal repo. The failure surfaces as GraphQLINSUFFICIENT_SCOPESinside an HTTP 200, not a 4xx.read:orgis being added to the injected PAT fleet-wide (see the PR-workflow bullet inmodules/agents/AGENTS.md); check withgh auth status. The REST PATCH stays the better call regardless — one request, no GraphQL preflight, no scope dependency.
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.
- 3d ago First seen · 58 lines · 123 tokens per session scan A bbf3bd09f7a1
cdn-upload is a skill published in the GitHub repository DJRHails/dotfiles (2 stars, last pushed 8d ago), licensed MIT. It adds 123 tokens to every session and 1,024 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
autopilot-batch
Fan out a batch of autopilot-queued issues to parallel background worktree subagents — each runs /autopilot at the build model from its 'model:' label — with a gating review at Opus 5 or above and never below the build (Opus reviews Sonnet and Opus builds, Fable reviews Fable builds).
todoist-cli
Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI. Use when the user wants to view, create, update, complete, or organize Todoist items, or mentions tasks, inbox, today, upcoming, projects, labels, or filters.
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
qa-handoff
Generate a hands-on QA testing guide as a self-contained HTML page — for Rails apps or static (Hugo) sites. --publish uploads the HTML to the project's configured QA host.
walkthrough
Generate a hands-on browser walkthrough of a PR's user-facing changes to exercise before review; --publish posts the final version to the PR for QA.
dustoff
Assess a project that's been dormant for months and produce a prioritized re-entry plan — lifecycle stage, what's stale or broken, and how far the project's tooling has drifted from current conventions — delegating every fix to the skill that owns it, and optionally capturing the plan as a tracking issue that survives…