Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Sassy-Dog/sassydog-skills/plugin install sassy-dogWrote 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/sassy-dog/sassydog-skills/github-issues)<a href="https://agentmods.dev/skills/sassy-dog/sassydog-skills/github-issues"><img src="https://agentmods.dev/badge/skills/sassy-dog/sassydog-skills/github-issues.svg" alt="Measured on agentmods" 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.00149 | $0.07182 |
| Opus 5 | $0.00075 | $0.03591 |
| Sonnet 5 | $0.00030 | $0.01436 |
| Haiku 4.5 | $0.00015 | $0.00718 |
Grade A, and why
github-issues 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Issue and ProjectV2 board operations for any GitHub repo: board snapshots, backlog reads, stale-issue detection, idempotent dedupe-then-file issue creation, and the fill/drain label-state transitions. Reads are free; this skill bundles exactly two write paths — scripts/file-or-link-issue.sh (issue creation, preview-then-confirm) and scripts/issue-claim.sh (label-state transitions plus promote's shape-gated assignee clear, dry-runnable) — plus one it points at, ${CLAUDE_PLUGIN_ROOT}/scripts/align-labels.sh, which owns the engineering-dimension and severity half of the label taxonomy.
Reads
Board snapshot (grouped by status column)
PROJECT_NUMBER=<n> OWNER=<org> bash ${CLAUDE_PLUGIN_ROOT}/skills/github-issues/scripts/board-snapshot.sh
Emits {counts, truncated, items[]}. If truncated: true, raise PROJECT_LIMIT — the newest issues are what got dropped. For board ID discovery (project/field/option IDs), card moves, and the board-vs-labels source-of-truth question, read references/board-graphql.md.
Backlog via labels
Some repos run label-driven backlogs with an empty board — an empty snapshot does not mean no backlog:
gh issue list --repo <R> --state open --limit 200 --json number,title,labels,updatedAt
Boardless work-queue snapshot (fill/drain)
One call replaces the per-tick ready/in-flight/blocked list reads AND parses the two machine-readable body contracts (touches: collision sets, literal Depends on #N lines) in one place:
REPO=<owner/name> bash ${CLAUDE_PLUGIN_ROOT}/skills/github-issues/scripts/queue-snapshot.sh
Emits {repo, me, ready[], in_flight[], blocked[]} — ready ordered number-ascending with touches/depends_on/unannotated per issue; in_flight carries a mine flag rather than silently filtering to @me, so a loop can count its own claims while still seeing other sessions'. Judgment (touches-set intersection, priority, the smell test) stays with the caller — this is a read, not a dispatcher.
What ships with it
9 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.
- references/board-graphql.md 3.3 KB
- references/dedupe-and-file.md 6.6 KB
- scripts/board-snapshot.sh 1.8 KB runs code
- scripts/file-or-link-issue.sh 20 KB runs code
- scripts/issue-claim.sh 61 KB runs code
- scripts/queue-snapshot.sh 5.7 KB runs code
- scripts/stale-issues.sh 25 KB runs code
- scripts/verify-gotcha-claims.sh 28 KB runs code
- scripts/verify-issue-refs.sh 39 KB runs code
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 Changed · +3 lines 7708c02da123
- 6d ago First seen · 252 lines · 149 tokens per session scan A fa466d345f1e
github-issues is a skill published in the GitHub repository Sassy-Dog/sassydog-skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 149 tokens to every session and 7,182 once invoked, about $0.0007 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
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…