What is pick-next-issue?

A workflow for choosing which open GitHub issue to work on next. GitHub issues are tracked reports or requests, and community engagement means reactions and comments from other users.

Use it to fetch open issues, rank them by reactions and comments, review the top candidates, and plan work on the issue you select.

It replaces guesswork with a ranked view of issues that appear to matter most to the project community.

pick-next-issue — Skill for Claude Code by tobihagemann/turbo

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 tobihagemann/turbo --skill pick-next-issue

Clone the repo

git clone --depth 1 https://github.com/tobihagemann/turbo

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 skills.

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/tobihagemann/turbo/pick-next-issue/github.svg)](https://agentmods.dev/skills/tobihagemann/turbo/pick-next-issue)

Your own site

<a href="https://agentmods.dev/skills/tobihagemann/turbo/pick-next-issue"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/pick-next-issue/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/tobihagemann/turbo/pick-next-issue"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/pick-next-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 563 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00053	$0.00563
Opus 5.5	$0.00021	$0.00225
Sonnet 5.5	$0.00011	$0.00113
Haiku 4.5	$0.00005	$0.00056

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

Security

Grade A, and why

pick-next-issue 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 3d 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.

claude/skills/pick-next-issue/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pick Next Issue

Rank open GitHub issues by engagement and plan the selected issue.

Step 1: Fetch and Rank Issues

Run gh issue list to fetch open issues with engagement data:

gh issue list --state open --json number,title,body,url,reactionGroups,comments,labels,createdAt --limit 50

Calculate an engagement score for each issue:

Reactions score: Sum all reaction counts from reactionGroups (thumbs up, heart, hooray, etc.). Weight thumbs-up (THUMBS_UP) reactions 2x since they signal explicit demand.
Comments score: Count of comments on the issue.
Engagement score: (weighted reactions) + comments

Sort issues by engagement score descending.

Step 2: Present Top 3

Present the top 3 issues in a numbered list. For each issue, show:

Title with issue number and link
Labels (if any)
Engagement: reaction breakdown and comment count
Created: date
First paragraph of the issue body (truncate if long)

If fewer than 3 open issues exist, present all of them.

If no open issues exist, inform the user and stop.

Step 3: User Picks an Issue

Ask the user to pick one of the presented issues (or request to see more).

If the user asks to see more, present the next 3 issues from the ranked list.

Step 4: Read the Full Issue

Fetch the complete issue details for the selected issue:

gh issue view <number> --json number,title,body,url,labels,comments,reactionGroups,assignees,milestone

Read the full issue body and comments to understand the requirements and any discussion context.

Step 5: Run `/plan` Skill

Run the /plan skill with the issue body as the task description. Tell /plan that the plan must include a final implementation step: "Close issue #N or reference it in the PR with Closes #N."

Rules

Requires gh CLI authenticated with access to the current repo
If gh fails (not in a repo, not authenticated), inform the user and stop
Never modify issues. This skill is read-only until the implementation is committed.

Read the full file on GitHub · 65 lines

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.

3d ago Changed · -24 tokens per session 71558607fc51
1mo ago Changed 492a17c4c127
2mo ago First seen · 65 lines · 77 tokens per session scan A 070dfa09b39c

Subscribe to this mod's changes

pick-next-issue is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 563 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-08-30.

Claude Code Planning Project management agent-skills claude-skills codex developer-tools skills

pick-next-issue next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pick-next-issuetobihagemann/turbo	Skill	420	today	MIT	A	53	Claude Code
offensive-c2-frameworksSnailSploit/Claude-Red	Skill	11k	yesterday	MIT	A	250	Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-Red	Skill	11k	yesterday	MIT	A	261	Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-Red	Skill	11k	yesterday	MIT	A	0	Claude Code, Codex
offensive-z-waveSnailSploit/Claude-Red	Skill	11k	yesterday	MIT	A	113	Claude Code, Codex
fiscalisteromainsimon/paperasse	Skill	2.6k	today	MIT	A	306	Claude Code
comptableromainsimon/paperasse	Skill	2.6k	today	MIT	A	248	Claude Code