Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/the-open-agent/oss-skillsnpx agentmods add skills/the-open-agent/oss-skills/issue-triageWrote 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/the-open-agent/oss-skills/issue-triage)<a href="https://agentmods.dev/skills/the-open-agent/oss-skills/issue-triage"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/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/the-open-agent/oss-skills/issue-triage"><img src="https://agentmods.dev/badge/skills/the-open-agent/oss-skills/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.00102 | $0.02166 |
| Opus 5 | $0.00051 | $0.01083 |
| Sonnet 5 | $0.00020 | $0.00433 |
| Haiku 4.5 | $0.00010 | $0.00217 |
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 10d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
An untriaged backlog is not a to-do list — it is a public record of requests you are ignoring. Every issue is either actionable, waiting on someone, or should be closed. There is no fourth state, and "open forever" is the one that quietly costs you contributors.
Issue forms beat templates
.yml forms produce structured, complete reports. Markdown templates get deleted by
the reporter and produce "it doesn't work".
# .github/ISSUE_TEMPLATE/bug_report.yml
name: Bug report
description: Something isn't working
labels: ["bug", "needs-triage"]
body:
- type: markdown
attributes:
value: |
Thanks for the report. Please check [existing issues](../issues?q=is%3Aissue) first.
- type: input
id: version
attributes: { label: Version, placeholder: "4.2.0" }
validations: { required: true }
- type: textarea
id: repro
attributes:
label: Reproduction
description: Minimal steps or a link to a minimal repo. This is the field that determines whether we can help.
validations: { required: true }
- type: textarea
id: expected
attributes: { label: Expected vs actual }
validations: { required: true }
- type: input
id: env
attributes: { label: OS and runtime, placeholder: "macOS 15.3, Node 22.11" }
Also add .github/ISSUE_TEMPLATE/config.yml to route non-bugs away from the tracker:
blank_issues_enabled: false
contact_links:
- name: Question or help
url: https://github.com/OWNER/REPO/discussions/categories/q-a
about: Ask in Discussions — questions here will be converted.
- name: Security vulnerability
url: https://github.com/OWNER/REPO/security/advisories/new
about: Report privately. Do not open a public issue.
Keep forms short. Every required field costs you some fraction of reports, and a bug you never hear about is worse than one reported imperfectly. Three fields that matter beat nine that produce abandonment.
A label set you will actually maintain
What ships with it
3 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.
- 10d ago First seen · 197 lines · 102 tokens per session scan A 54a4dc9979d1
issue-triage is a skill published in the GitHub repository the-open-agent/oss-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 2,166 once invoked, about $0.0005 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-31.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
jira-server-pat-cli
A command-line workflow for managing self-hosted Jira Server or Jira Data Center through Jira's REST API. Jira is a system for tracking issues, projects, work, and software tasks.
issue-comment
Handle a non-build maintainer comment on an issue or PR — close, reopen, label, dedupe, answer a brief question, or triage. Action-only; redirect anything that needs code changes to /build.
github-issues
GitHub issue'larını gh veya REST ile oluştur, sırala, etiketle, ata.
phase-closeout
A Chinese-language stage closer that summarizes completed work, records decisions, updates project status, and prepares the next conversation.
handoff
Use when leaving a project, joining a project, or performing any project/module handover. Detects .handoff/ directory presence but always confirms intent before acting.