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 runxhq/runx --skill github-issue-triagegit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/github-issue-triage)<a href="https://agentmods.dev/skills/runxhq/runx/github-issue-triage"><img src="https://agentmods.dev/badge/skills/runxhq/runx/github-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/runxhq/runx/github-issue-triage"><img src="https://agentmods.dev/badge/skills/runxhq/runx/github-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.00031 | $0.00989 |
| Opus 5.5 | $0.00012 | $0.00396 |
| Sonnet 5.5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
github-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 today.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Triage
Turn a noisy issue queue into one evidence-backed next action. The skill helps a maintainer decide which thread deserves attention and how to respond without silently mutating a repository or inventing state that is not present in the thread snapshot.
Discovery and response are separate jobs. The default provider-respond runner
reads one issue through the GitHub instance selected here, the signed-in gh
session or a stored token, binds the returned snapshot and readback into the
receipt, and turns it into a concise profile,
recommended posture, draft reply, and follow-up plan. discover and respond
remain explicit supplied-evidence lanes for offline queues and replay. Every
analysis lane stops at a draft. Select post explicitly to consume that exact
packet under a scoped comment grant and require provider readback without
repeating triage.
When to use it
Use the default runner when the operator has a repository and issue number and
wants current provider-grounded evidence. Use discover for a supplied issue
queue and respond when an exact snapshot is already available or a receipt is
being replayed. Use code-intake when the material must first become an
engineering change request, and github-issue-to-pr only after explicit promotion to
implementation.
Do not use the analysis runners to close, label, assign, comment on, or promise
work in a repository. They prepare the maintainer decision and draft only; the
explicit post runner performs only the exact accepted comment.
Evidence and provider boundary
Every candidate and response is bound through Runx's native data digest to the
exact issue snapshot or bounded snapshot set. provider-respond obtains that
snapshot through github/issue.read with repo.read, and the provider
operation remains in the sealed run alongside the draft. post comments
through github/comments.create, which completes only when the read-back
comment matches the exact accepted body. Supplied snapshots are labelled as
such rather than promoted to provider readback.
What ships with it
11 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.
- fixtures/bin/gh 205 B
- fixtures/composes-in-graph.yaml 472 B
- fixtures/default-reads-and-drafts-response.yaml 2.3 KB
- fixtures/default-requires-github-binding.yaml 594 B
- fixtures/discover-bounded-snapshots.yaml 1.0 KB
- fixtures/invented-issue-ref-rejected.yaml 1013 B
- fixtures/respond-from-snapshot.yaml 2.1 KB
- fixtures/support/composed.graph 682 B
- github-issue-triage.mjs 5.6 KB runs code
- references/catalog.md 158 B
- run.yaml 10 KB
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.
- today First seen · 99 lines · 31 tokens per session scan A df666eb2dbd3
github-issue-triage is a skill published in the GitHub repository runxhq/runx (103 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 989 once invoked, about $0.0001 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-10-18.
Other skills, from other repositories
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
aigon-next
Suggest the most likely next workflow action based on current context.
aigon-feature-reset
Reset feature - remove worktrees, branches, state, and return lifecycle to backlog.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…