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/dwmkerr/claude-code-agent/github-attach-imagesnpx skills add dwmkerr/claude-code-agent --skill github-attach-imagesgit clone --depth 1 https://github.com/dwmkerr/claude-code-agentWhat 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.00018 | $0.00481 |
| Opus 5 | $0.00009 | $0.00241 |
| Sonnet 5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
GitHub Attach Images 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 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.
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.
What it actually says
GitHub Attach Images
Attach images to GitHub PRs or issues by hosting them in a scratch repo.
When to use
- Adding screenshots to PR comments
- Attaching images to issue comments
- Any GitHub comment needing embedded images
Setup scratch repo
-
Clone or create scratch repo
git clone [email protected]:<USERNAME>/scratch.git /tmp/scratchIf it doesn't exist, create a public repo called
scratchfirst. -
Folder structure
scratch/ └── github-attachments/ └── <org>_<repo>_<pr-or-issue>/ ├── 01-screenshot.png └── 02-screenshot.png
Add images
-
Copy images to scratch repo
mkdir -p /tmp/scratch/github-attachments/<org>_<repo>_<number> cp /path/to/screenshots/*.png /tmp/scratch/github-attachments/<org>_<repo>_<number>/ -
Push to GitHub
cd /tmp/scratch git add . git commit -m "chore: images for <org>/<repo>#<number>" git push
Attach to PR or issue
Comment on PR:
gh pr comment <NUMBER> --repo <org>/<repo> --body "$(cat <<'EOF'
## Screenshots
This shows...
EOF
)"
Comment on issue:
gh issue comment <NUMBER> --repo <org>/<repo> --body "$(cat <<'EOF'
EOF
)"
Image URL format
https://raw.githubusercontent.com/<USERNAME>/scratch/main/github-attachments/<org>_<repo>_<number>/<filename>
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 · 76 lines · 18 tokens per session scan A 62952e881e0f
GitHub Attach Images is a skill published in the GitHub repository dwmkerr/claude-code-agent (7 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 481 once invoked, about $0.0001 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-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.