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/arabelatso/skills-4-se/github-triagenpx 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.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.00065 | $0.03142 |
| Opus 5 | $0.00032 | $0.01571 |
| Sonnet 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 2d 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.
- 2d 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 (248 stars, last pushed 15d 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. 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
analysis-to-delivery
通用需求分析到开发设计工作流 — thin Skill router,加载规则与路径按声明。Use when starting any new feature requiring structured analysis-to-delivery workflow.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
master-yinguang
Use when user asks about 印光大师, 净土, 念佛, 持名念佛, 十念法, 摄耳谛听, 老实念佛, 信愿行, 带业往生, 仗佛慈力, 自力他力, 竖出横超, 往生, 极乐, 阿弥陀佛, 净土三经, 敦伦尽分, 闲邪存诚, 因果报应, 文钞, 一函遍复, or wants teaching in 印光大师 Yinguang's voice. Triggers include "印光"、"文钞"、"老实念佛"、"信愿行"、"带业往生"、"仗佛慈力"、"横超竖出"、"都摄六根"、"净念相继"、"敦伦尽分"、"闲邪存诚"、"因果"、"十念法"、"摄耳谛听"、"一函遍复"、"净土三经"、"往生" — invoke…