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 ArabelaTso/Skills-4-SE --skill github-triagegit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/github-triage)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/github-triage"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/github-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/arabelatso/skills-4-se/github-triage"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/github-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.03142 |
| Opus 5.5 | $0.00026 | $0.01257 |
| Sonnet 5.5 | $0.00013 | $0.00628 |
| Haiku 4.5 | $0.00006 | $0.00314 |
Grade A, and why
github-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 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Triage — Unified Issue & PR Processor
You are a GitHub triage orchestrator. You fetch all open issues and PRs, classify each one, then process each item in parallel. Each item gets analyzed, actioned (comment/close/merge/report), and results are tracked.
ARCHITECTURE
1 issue or PR = 1 parallel task
| Rule | Value |
|---|---|
| Execution mode | All items processed in parallel |
| Result tracking | Each item produces a structured report |
| Result collection | Stream results as they arrive |
PHASE 1: FETCH ALL OPEN ITEMS
Run these commands to collect data:
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
# Issues: all open
gh issue list --repo $REPO --state open --limit 500 \
--json number,title,state,createdAt,updatedAt,labels,author,body,comments
# PRs: all open
gh pr list --repo $REPO --state open --limit 500 \
--json number,title,state,createdAt,updatedAt,labels,author,body,headRefName,baseRefName,isDraft,mergeable,reviewDecision,statusCheckRollup
If either returns exactly 500 results, paginate using --search "created:<LAST_CREATED_AT" until exhausted.
PHASE 2: CLASSIFY EACH ITEM
For each item, determine its type based on title, labels, and body content:
Issues
| Type | Detection | Action Path |
|---|---|---|
ISSUE_QUESTION |
Title contains [Question], [Discussion], ?, or body is asking "how to" / "why does" / "is it possible" |
HANDLE_ISSUE_QUESTION |
ISSUE_BUG |
Title contains [Bug], Bug:, body describes unexpected behavior, error messages, stack traces |
HANDLE_ISSUE_BUG |
ISSUE_FEATURE |
Title contains [Feature], [RFE], [Enhancement], Feature Request, Proposal |
HANDLE_ISSUE_FEATURE |
ISSUE_OTHER |
Anything else | HANDLE_ISSUE_OTHER |
PRs
| Type | Detection | Action Path |
|---|---|---|
PR_BUGFIX |
Title starts with fix, fix:, fix(, branch contains fix/, bugfix/, or labels include bug |
HANDLE_PR_BUGFIX |
PR_OTHER |
Everything else (feat, refactor, docs, chore, etc.) | HANDLE_PR_OTHER |
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 · 348 lines · 65 tokens per session scan A 6d4ef9c37d93
github-triage is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (257 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 3,142 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-09-03.
Other skills, from other repositories
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.
skill-pr-review
Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.