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 skills add pivoshenko/pivoshenko.ai --skill git-issue-triagegit clone --depth 1 https://github.com/pivoshenko/pivoshenko.aiWrote 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/pivoshenko/pivoshenko.ai/git-issue-triage)<a href="https://agentmods.dev/skills/pivoshenko/pivoshenko.ai/git-issue-triage"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/git-issue-triage/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/pivoshenko/pivoshenko.ai/git-issue-triage"><img src="https://agentmods.dev/badge/skills/pivoshenko/pivoshenko.ai/git-issue-triage.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.00204 | $0.02581 |
| Opus 5.5 | $0.00082 | $0.01032 |
| Sonnet 5.5 | $0.00041 | $0.00516 |
| Haiku 4.5 | $0.00020 | $0.00258 |
Grade A, and why
git-issue-triage 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 29d 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.
Git Issue Triage
Groom the open backlog. Read-only sweep -> bucketed report -> per-category confirm -> apply -> verify.
Report what the sweep returned, never what this file predicts. The buckets below define how to classify; the contents come from the run.
Flow
-
Sweep, read-only, two calls total:
gh issue list --state open --limit 200 --json number,title,labels,assignees,createdAt,updatedAt,body gh label list --limit 200 --json name -q '.[].name'Why -> one batched fetch, never
gh issue viewper issue. A 60-issue backlog is 60 round trips that way, and the list payload carries every field the buckets need except the Stale comment count, fetched per Stale. Notcomments- that field returns every comment body for every open issue, a context blowout on exactly the big backlogs this skill targets. 200 rows returned -> the cap was hit and the sweep is not authoritative; raise--limitor paginate before bucketing, and say so in the report -
Zero open issues -> say so, stop. No report, no proposals
-
Corroborating fetch, only if step 1 produced Closeable candidates:
gh search prs --repo "$(gh repo view --json nameWithOwner -q .nameWithOwner)" --merged --limit 100 --json number,title,bodyGrep those bodies for
#<n>. Why -> a merged PR naming the issue is the only close signal that does not require reading the tree. 100 rows returned -> the cap was hit; raise--limitor paginate before treating the grep as evidence -
Bucket every open issue into exactly one category. See Buckets
-
Report. One line per issue, grouped, counts in each heading. See Report Format
-
Confirm per category, never per issue and never all-at-once.
AskUserQuestion, multiSelect, one option per non-empty actionable category. Why -> closing is irreversible in effect even though technically reopenable, relabelling is not, and the user is entitled to accept "labels yes, closes no" -
Apply only the accepted categories, batched. See Apply
-
Summary: counts applied per category, plus one line per skipped issue with why. No recap of what step 5 already listed
What ships with it
1 file 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.
- 29d ago Changed · -29 lines 7754f4afd682
- 1mo ago Changed 81f5ba5e0b73
- 1mo ago First seen · 218 lines · 204 tokens per session scan A 7f8d3e0da8dd
git-issue-triage is a skill published in the GitHub repository pivoshenko/pivoshenko.ai (6 stars, last pushed yesterday), licensed MIT. It adds 204 tokens to every session and 2,581 once invoked, about $0.0008 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-09-14.
Other skills, from other repositories
ghpm-issue
File a GitHub issue and add it to the project board. Works mid-session or standalone. Reads .ghpm/config.json for repo list and project.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
github-issue
Use when opening a GitHub issue, bug report, feature request, or discussion in any repository, including one the user has no local checkout of.
setup
Configure this repo's issue tracker for the flow skills: GitHub, Jira, or local markdown (the default).
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.