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/jimmypaolini/codebase/github-issuesnpx skills add JimmyPaolini/codebase --skill github-issuesgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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.00141 | $0.02003 |
| Opus 5 | $0.00071 | $0.01001 |
| Sonnet 5 | $0.00028 | $0.00401 |
| Haiku 4.5 | $0.00014 | $0.00200 |
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 today.
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.
This is a copy
97% identical to github-issues — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Manage GitHub issues using the @modelcontextprotocol/server-github MCP server.
Available Tools
MCP Tools (read operations)
| Tool | Purpose |
|---|---|
mcp__github__issue_read |
Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) |
mcp__github__list_issues |
List and filter repository issues by state, labels, date |
mcp__github__search_issues |
Search issues across repos using GitHub search syntax |
mcp__github__projects_list |
List projects, project fields, project items, status updates |
mcp__github__projects_get |
Get details of a project, field, item, or status update |
mcp__github__projects_write |
Add/update/delete project items, create status updates |
CLI / REST API (write operations)
The MCP server does not currently support creating, updating, or commenting on issues. Use gh api for these operations.
| Operation | Command |
|---|---|
| Create issue | gh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=... |
| Update issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... -f state=... |
| Add comment | gh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=... |
| Close issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed |
| Set issue type | Include -f type=Bug in the create call (REST API only, not supported by gh issue create CLI) |
Note: gh issue create works for basic issue creation but does not support the --type flag. Use gh api when you need to set issue types.
Workflow
- Determine action: Create, update, or query?
- Gather context: Get repo info, existing labels, milestones if needed
- Structure content: Use appropriate template from references/templates.md
- Execute: Use MCP tools for reads,
gh apifor writes - Confirm: Report the issue URL to user
Creating Issues
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.
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.
- today First seen · 203 lines · 141 tokens per session scan A 3143f6431a5a
github-issues is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 141 tokens to every session and 2,003 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to github-issues, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…