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/jackchuka/ghpmnpx agentmods add skills/jackchuka/ghpm/ghpm-issueWrote 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/jackchuka/ghpm/ghpm-issue)<a href="https://agentmods.dev/skills/jackchuka/ghpm/ghpm-issue"><img src="https://agentmods.dev/badge/skills/jackchuka/ghpm/ghpm-issue/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/jackchuka/ghpm/ghpm-issue"><img src="https://agentmods.dev/badge/skills/jackchuka/ghpm/ghpm-issue.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.00036 | $0.01656 |
| Opus 5.5 | $0.00014 | $0.00662 |
| Sonnet 5.5 | $0.00007 | $0.00331 |
| Haiku 4.5 | $0.00004 | $0.00166 |
Grade A, and why
ghpm-issue 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 1mo 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghpm-issue
PREREQUISITE: Read
../ghpm-shared/SKILL.mdfor prerequisites and error handling.
File a GitHub issue and add it to the project board in one step. Works mid-session (during ghpm-work) or standalone.
Arguments
/ghpm-issue— interactive: asks for title and body/ghpm-issue <title>— uses argument as issue title, asks for optional body
Workflow
Phase 1: Setup
-
Startup sequence: Follow the startup sequence in
../ghpm-shared/SKILL.md. This loads config, refreshes cache if stale, and checks for stale sessions.Extract from config:
config.project— id, owner, number, titleconfig.repos— eligible repositoriesconfig.workflow— columns, field_idconfig.fields— project fields with name, id, type, optionsconfig.conventions— natural language rules (if present)
Phase 2: Gather Info
-
Title and body:
- If argument provided, use as title. Ask for an optional body (user can skip).
- If no argument, ask for title, then ask for optional body.
-
Pick repo:
- If
config.reposhas one entry → use it. - If
config.reposis empty or missing → ask the user to specify a repo inowner/repoformat. - If
config.reposhas multiple entries → present a numbered list and ask.
- If
-
Link to active session: Find active session per
../ghpm-shared/references/session.md(match current branch against session files). If found, prepend to the issue body:Related to <repo>#<num> <original body>
Phase 3: Infer Metadata
All inference is best-effort. Skip silently when no confident match exists.
-
Infer labels: Fetch the target repo's actual labels:
gh label list -R <repo> --json name,description --jq '.[] | "\(.name)\t\(.description)"'Match the issue title and body against the fetched label names and descriptions (case-insensitive substring/keyword matching). Only use labels that exist on the repo — never assume a label exists.
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.
- 1mo ago First seen · 178 lines · 36 tokens per session scan A 667c9a4468e9
ghpm-issue is a skill published in the GitHub repository jackchuka/ghpm (20 stars, last pushed 10d ago), licensed MIT. It adds 36 tokens to every session and 1,656 once invoked, about $0.0001 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-30.
Other skills, from other repositories
git-issue-triage
Groom an open GitHub backlog with gh - one read-only sweep, every open issue bucketed into exactly one category (unlabeled, unprioritized, stale, likely duplicate, closeable, blocked, healthy), a per-issue report, per-category confirmation, then batched label / state / comment edits. Use when the user says "triage…
git-issue-create
Open one standalone GitHub issue with gh - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request however casual: "open an issue", "file a bug", "make a ticket", "/git-issue-create", "track this", "note this down", "we should fix X later", or…
git-issue-start
Take a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its type: label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take…
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.