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/buildinternet/uploads/github-screenshotsnpx skills add buildinternet/uploads --skill github-screenshotsgit clone --depth 1 https://github.com/buildinternet/uploadsWhat 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.00278 | $0.04118 |
| Opus 5 | $0.00139 | $0.02059 |
| Sonnet 5 | $0.00056 | $0.00824 |
| Haiku 4.5 | $0.00028 | $0.00412 |
Grade A, and why
github-screenshots 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 yesterday.
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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshots and recordings in GitHub PRs and issues
Why this exists
GitHub's native image hosting (github.com/user-attachments/…) only works
from an authenticated browser session — there is no gh CLI or REST endpoint
for it. Any image URL in a PR/issue body written with gh … --body-file must
already point at something publicly hosted. The uploads CLI and the
hosted MCP at https://agents.uploads.sh/mcp both host the file on uploads.sh
and return a stable public URL plus ready-to-paste markdown.
Which surface
Pick one transport and stay on it. This skill is the workflow. The uploads-cli skill owns flags and MCP tool contracts.
| You have | Use |
|---|---|
| No shell (ChatGPT, or any host without a checkout) | Hosted MCP put with (contentBase64 + filename, or contentUrl) + repo + (pr or branch). Filename is optional with contentUrl when the URL path has a leaf. Embed the returned markdown / embedUrl. Never imply you can run uploads attach ./shot.png. |
A checkout and the uploads binary |
The CLI examples below. Git can fill repo / branch. |
A localhost page or a selector annotate |
CLI only (uploads screenshot --via local). Remote render cannot reach your machine. |
| Neither MCP nor the CLI | Stop and say so. Do not treat npm install -g as the ChatGPT path. |
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.
- yesterday First seen · 326 lines · 278 tokens per session scan A e7d2dde1c9b1
github-screenshots is a skill published in the GitHub repository buildinternet/uploads (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 278 tokens to every session and 4,118 once invoked, about $0.0014 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
open-pr
Take a cloudflare/agents GitHub issue plus any repro findings and one-shot a fix PR — branch, change, test, push, and open the PR linked to the issue.
release-notes
Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.
test-plan
Produce a focused test plan for a change. Use when the user asks how to test a feature, what cases to cover, or for a QA checklist before shipping.
workspace-digest
Summarize the files saved in this assistant's shared workspace. Use when the user asks what is in their workspace, for a file inventory, or a digest of saved work.
debug-plan
Create a systematic debugging plan for a bug report. Use when the user asks how to investigate a failure, regression, or unexpected behavior.
pirate-voice
Rewrite or answer in a playful pirate voice. Use when the user asks for pirate tone, nautical phrasing, or says to talk like a pirate.