Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jerseycheese/agent-skillsnpx agentmods add skills/jerseycheese/agent-skills/github-screenshotWrote 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/jerseycheese/agent-skills/github-screenshot)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/github-screenshot"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/github-screenshot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/github-screenshot"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/github-screenshot.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00067 | $0.01261 |
| Opus 5.5 | $0.00027 | $0.00504 |
| Sonnet 5.5 | $0.00013 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
github-screenshot 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Screenshot Helper
When to Use This Skill
Use this skill when:
- Adding screenshots to PR descriptions
- Including images in GitHub issues
- Documenting features with screenshots
- Creating visual documentation in markdown
Setup
This skill wraps a local generate-github-image-markdown.sh script. Update the path below to match your own installation before using.
Directory convention
When the image is being committed purely so it can render in an issue/PR body (not an existing app asset the user is pointing you at), commit it under a top-level github-screenshots/<topic-or-issue>/ directory — e.g. github-screenshots/hover-text-invisible/before-hover.png. The name says what these files are for: throwaway evidence for a GitHub body, not app screenshots or fixtures, so they're easy to find and prune later without touching anything else in the repo. Don't reuse a generic screenshots/ dir for this — that name doesn't self-document, and it collides with whatever ad-hoc convention a given repo might already have for actual app screenshots.
If the target repo already has an established convention for this (check with the user or look for precedent — e.g. git log --diff-filter=A --name-only --all | grep -iE 'screenshot'), follow that instead of introducing a second one.
What This Skill Does
Runs your generate-github-image-markdown.sh script to:
- Generate proper raw.githubusercontent.com URLs
- Create markdown with alt text and captions
- Handle git repository detection automatically
- Include helpful comments with local paths
Usage Flow
Step 1: Gather Information
Ask the user for:
- Image path (required) - relative or absolute
- Alt text (optional) - defaults to "Screenshot"
- Caption (optional) - italicized description below image
Step 2: Run the Script
Execute:
~/tools/screenshots/generate-github-image-markdown.sh \
"$IMAGE_PATH" \
"$ALT_TEXT" \
"$CAPTION"
Permission pattern needed (update path to match your setup):
Bash(~/tools/screenshots/generate-github-image-markdown.sh:*)
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 Changed · -1 lines · -15 tokens per session b26bda358dfa
- 1mo ago First seen · 190 lines · 82 tokens per session scan A 3e58ae619bfc
github-screenshot is a skill published in the GitHub repository jerseycheese/agent-skills (3 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,261 once invoked, about $0.0003 per session on Opus 5.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
github
GitHub issues, pull requests, repos, code search, releases, gists, stars, watching, forks, and Actions via the gh CLI. Use when the user mentions GitHub, an issue/PR number, a repo, a commit, a release, a gist, or code review.
gitlab
GitLab issues, merge requests, repositories, CI pipelines, and code search via the glab CLI. Use when the user mentions GitLab, an MR/issue number, a project on gitlab.com, or a self-hosted GitLab instance.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
spk-admin-git-workflow
Operate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery.
spk-gate-merge
Merge an accepted Spec Kitty mission safely, preserving git invariants, mission state, and post-merge follow-through.