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/teaonly/skill.mk/github-triagenpx skills add Teaonly/SKILL.mk --skill github-triagegit clone --depth 1 https://github.com/Teaonly/SKILL.mkWhat 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.00050 | $0.02204 |
| Opus 5 | $0.00025 | $0.01102 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- github-triage — 98% identical, 2 lines differ
- github-triage — 86% identical, 45 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Triage
Triage issues in the current repo using a label-based state machine. Infer the repo from git remote. Use gh for all GitHub operations.
AI Disclaimer
Every comment or issue posted to GitHub during triage must include the following disclaimer at the top of the comment body, before any other content:
> *This was generated by AI during triage.*
Reference docs
- AGENT-BRIEF.md — how to write durable agent briefs
- OUT-OF-SCOPE.md — how the
.out-of-scope/knowledge base works
Labels
| Label | Type | Description |
|---|---|---|
bug |
Category | Something is broken |
enhancement |
Category | New feature or improvement |
needs-triage |
State | Maintainer needs to evaluate this issue |
needs-info |
State | Waiting on reporter for more information |
ready-for-agent |
State | Fully specified, ready for AFK agent |
ready-for-human |
State | Requires human implementation |
wontfix |
State | Will not be actioned |
Every issue should have exactly one state label and one category label. If an issue has conflicting state labels (e.g. both needs-triage and ready-for-agent), flag the conflict and ask the maintainer which state is correct before doing anything else. Provide a recommendation.
State Machine
| Current State | Can transition to | Who triggers it | What happens |
|---|---|---|---|
unlabeled |
needs-triage |
Skill (on first look) | Issue needs maintainer evaluation. Skill applies label after presenting recommendation. |
unlabeled |
ready-for-agent |
Maintainer (via skill) | Issue is already well-specified and agent-suitable. Skill writes agent brief comment, applies label. |
unlabeled |
ready-for-human |
Maintainer (via skill) | Issue requires human implementation. Skill writes a brief comment summarizing the task, applies label. |
unlabeled |
wontfix |
Maintainer (via skill) | Issue is spam, duplicate, or out of scope. Skill closes with comment (and writes .out-of-scope/ for enhancements). |
needs-triage |
needs-info |
Maintainer (via skill) | Issue is underspecified. Skill posts triage notes capturing progress so far + questions for reporter. |
needs-triage |
ready-for-agent |
Maintainer (via skill) | Grilling session complete, agent-suitable. Skill writes agent brief comment, applies label. |
needs-triage |
ready-for-human |
Maintainer (via skill) | Grilling session complete, needs human. Skill writes a brief comment summarizing the task, applies label. |
needs-triage |
wontfix |
Maintainer (via skill) | Maintainer decides not to action. Skill closes with comment (and writes .out-of-scope/ for enhancements). |
needs-info |
needs-triage |
Skill (detects reply) | Reporter has replied. Skill surfaces to maintainer for re-evaluation. |
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.
- 2d ago First seen · 169 lines · 50 tokens per session scan A 747bef391201
github-triage is a skill published in the GitHub repository Teaonly/SKILL.mk (102 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 2,204 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-08-30.
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…