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 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/issue-triage)<a href="https://agentmods.dev/skills/runxhq/runx/issue-triage"><img src="https://agentmods.dev/badge/skills/runxhq/runx/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/issue-triage"><img src="https://agentmods.dev/badge/skills/runxhq/runx/issue-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.00029 | $0.01024 |
| Opus 5 | $0.00015 | $0.00512 |
| Sonnet 5 | $0.00006 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on 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 Runx's provider boundary—preferring an authenticated
local gh session and using Connect only when explicitly selected or needed—
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 issue-intake when the material must first become an
engineering change request, and 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 native provider.read with repo.read, and the provider
operation remains in the sealed run alongside the draft. The mcp-read runner composes the
bundled examples/github-mcp-hero/read-issue provider pattern for deterministic
tests; it is not evidence that live GitHub was queried. Supplied snapshots are
labelled as such rather than promoted to provider readback.
What ships with it
7 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.
- 8d ago First seen · 102 lines · 29 tokens per session scan A 9b836d6b8981
issue-triage is a skill published in the GitHub repository runxhq/runx (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,024 once invoked, about $0.0001 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
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.