Use it across selected GitHub repositories to prioritize issues and establish the requirements an agent or developer should meet.

It helps turn an unprepared issue list into clearer, ordered work without mixing issue triage with implementation or code review.

github-issue-triage — Skill for Claude Code and Codex by OpenHands

Q: What is github-issue-triage?

An automation that reviews open GitHub issues, ranks their priority, and adds acceptance criteria before marking them ready for development. Acceptance criteria are conditions that define when an issue is complete.

Install

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.

Any agent

npx skills add OpenHands/extensions --skill github-issue-triage

Clone the repo

git clone --depth 1 https://github.com/OpenHands/extensions

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/openhands/extensions/github-issue-triage/github.svg)](https://agentmods.dev/skills/openhands/extensions/github-issue-triage)

Your own site

<a href="https://agentmods.dev/skills/openhands/extensions/github-issue-triage"><img src="https://agentmods.dev/badge/skills/openhands/extensions/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/openhands/extensions/github-issue-triage"><img src="https://agentmods.dev/badge/skills/openhands/extensions/github-issue-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 351 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.00351
Opus 5.5	$0.00009	$0.00140
Sonnet 5.5	$0.00004	$0.00070
Haiku 4.5	$0.00002	$0.00035

Measured 11d ago against content hash 92f840e246b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 11d ago.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/agent_conversation.py, scripts/github_client.py, scripts/triage_publication.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/github-issue-triage/SKILL.md · 38 lines

What it actually says

GitHub issue triage

Prioritize open issues and establish acceptance criteria before marking them ready for development.

Setup

Keep triage separate from implementation and review. Follow README.md for packaging, credentials, publisher setup, and limits. Never put token values in the automation definition or prompt. Legacy agent publication is the default.

Triage instructions

Honor explicit dependencies. Read applicable root/local AGENTS.md, .agents/skills/custom-codereview-guide.md if present, human discussion, and adjacent code. Identify affected versions and the owning component (Canvas, SDK, automation, or extensions).
Follow current human decisions over stale generated criteria. Do not repeat answered questions. Keep scope bounded, name non-goals, and ask only unresolved material product/design questions.
Define observable completion, not entry requirements. Do not require tests for unwritten code, PR artifacts, or images/videos for every issue. Default priority to low; medium/high need recorded real user pain, not speculation or synthetic tests.
Return structured recommendations. If a publisher is configured, use it; never bypass it or its changed-input checks. Legacy direct mode follows the same rules without enforcement.
Preserve human text and unrelated labels. Never run repository checkers with credentials. Use current repository policy audited by the deployment owner, not historical checker comments, to decide readiness.
Do not implement code or accept pull requests.

Files

What ships with it

9 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.

Changes

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.

11d ago Changed · -20 lines 92f840e246b2
25d ago Changed · +23 lines eec8e8f6d1c9
1mo ago Changed · -3 lines d8a79d0cc8a0
1mo ago First seen · 38 lines · 22 tokens per session scan A 2c537ae9e5c2

Subscribe to this mod's changes

github-issue-triage is a skill published in the GitHub repository OpenHands/extensions (167 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 351 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-09-15.

Planning Project management

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens