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 sammcj/agentic-coding --skill github-triagegit clone --depth 1 https://github.com/sammcj/agentic-codingWrote 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/sammcj/agentic-coding/github-triage)<a href="https://agentmods.dev/skills/sammcj/agentic-coding/github-triage"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/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/sammcj/agentic-coding/github-triage"><img src="https://agentmods.dev/badge/skills/sammcj/agentic-coding/github-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 39 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00050 | $0.02181 |
| Opus 5.5 | $0.00020 | $0.00872 |
| Sonnet 5.5 | $0.00010 | $0.00436 |
| Haiku 4.5 | $0.00005 | $0.00218 |
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.
Copies of this mod
3 near-identical copies found in the catalogue:
- github-triage — 91% identical, 25 lines differ
- github-triage — 91% identical, 22 lines differ
- github-triage — 89% identical, 22 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
2 files 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.
- 1mo ago First seen · 169 lines · 50 tokens per session scan A f3c40036968f
github-triage is a skill published in the GitHub repository sammcj/agentic-coding (165 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 2,181 once invoked, about $0.0002 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
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
herdr-kit-workflows
Set up and operate Herdr Kit safely: install and configure the plugin and Mastra Code integration, manage Review and Work repository scope, open primary repository workspaces, synchronize managers, materialize or dematerialize managed worktrees, and update Herdr Kit settings or shortcuts.
herdr-manager-query
Query the authoritative global Herdr Review and Work Manager inventory, recommend actionable PR work, and explicitly materialize confirmed remote-only Review Manager records through the plugin's stable public CLI.
jira-execute
Implement a Jira issue, open a pull request, and report the work on the issue. Insert into the prompt of a Jira column rule that does the building.