A workflow step that helps choose the next GitHub issue, creates its branch, and records it locally for work to begin.

Use it to choose parked or open issues, filter candidates by label, or start a general-fixes issue.

It gives you a consistent way to select pending work and prepare the project before planning or implementation.

iflow-pick — Skill by jepegit

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.

agentmods

npx agentmods add skills/jepegit/issue-flow/iflow-pick

Any agent

npx skills add jepegit/issue-flow --skill iflow-pick

Clone the repo

git clone --depth 1 https://github.com/jepegit/issue-flow

Made for: Claude Code, Codex, Cursor.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00025	$0.02440
Opus 5	$0.00013	$0.01220
Sonnet 5	$0.00005	$0.00488
Haiku 4.5	$0.00003	$0.00244

Measured 2d ago against content hash ae2c51a3355e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

iflow-pick 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 2d 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.

.cursor/skills/iflow-pick/SKILL.md · 120 lines

How it starts

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

issue-flow — pick next issue (`/iflow-pick`)

Follow this skill to help the user choose what to work on next (parked work first, else ranked open GitHub issues) and get set up to start.

Do not use this skill from /iflow, /iflow-build, or /iflow-close. /iflow-pick is explicit-only because it creates GitHub issues and branches.

Input

(nothing) — survey candidates and ask which to pick.
fix — create a new general-fixes GitHub issue (a fresh one every time) and use it.
label:<L> — hard filter: shortlist only open issues that carry GitHub label <L> (case-insensitive; strip whitespace after the colon). Compatible with noplan / root: / repo:. Empty after filter → stop (“no open issues with label <L>”). Never auto-pick even when only one match. For batch processing the same filter, use /iflow-cycle label:<L> (or /iflow-cycle yolo for the configured yolo trigger).
a hint (milestone / topic) — soft-bias the candidate ranking when label:<L> is absent. Free-form text that happens to name a label is not a hard filter — use the label: token.
noplan — skip the auto_plan chain for this run (ask before /iflow-plan even when auto_plan is true).

Invoke: type iflow pick in chat, or /iflow-pick from the slash menu (iflow-pick also works).

MODEL & EXECUTION DIRECTIVE

Profile: reasoning — Prioritize deep thinking and careful trade-offs over speed or token economy.

In Cursor: switch to a thinking-capable model before invoking this step (not Auto-only).

Keep scope tight to what this step requires.

Resolve project root (multi-root workspaces)

Before any git, gh, or .issueflows/ path operation in this workflow:

Resolution order (stop when unambiguous):

Explicit hints in slash input — root:<path>, repo:<folder-basename> (directory name, e.g. cellpy-core), or repo:owner/name.
CLI fast path — issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returned project_root and repo; pass -C <project_root> to other issue-flow agent … subcommands. When the answer came from the workspace registry, the payload sets resolved_via_workspace_default: true.
Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
Workspace default — an issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member repo; use it when no scaffold matched above. Tell the user the default was used.
Ambiguous → stop and ask; never guess between sibling repos.

Read the full file on GitHub · 120 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.

2d ago First seen · 120 lines · 25 tokens per session scan A ae2c51a3355e

Subscribe to this mod's changes

iflow-pick is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 2,440 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-08-31.

Git and workflow Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens