Borrowing it
Nothing to install: this file belongs to jepegit/issue-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jepegit/issue-flow/main/.cursor/skills/iflow-pick/SKILL.mdgit clone --depth 1 https://github.com/jepegit/issue-flowWrote 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/jepegit/issue-flow/iflow-pick)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-pick"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-pick/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/jepegit/issue-flow/iflow-pick"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-pick.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.00038 | $0.02326 |
| Opus 5.5 | $0.00015 | $0.00930 |
| Sonnet 5.5 | $0.00008 | $0.00465 |
| Haiku 4.5 | $0.00004 | $0.00233 |
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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — pick and capture (/iflow-pick)
Help the user choose what to work on next (parked work first, else ranked open GitHub issues), create the branch, and capture the issue under .issueflows/01-current-issues/.
/iflow dispatches here only to capture an already-known issue <N> (no selection, no new GitHub issue).
Input
- (nothing) — survey candidates and ask which to pick.
<N>, a URL, orowner/repo#N— the issue is chosen: skip Phase 1 and go to Phase 2. On an issue-style branch<N>-<slug>with nothing captured yet, only capture (Phase 2 step 3).capture [<N>]— capture only: readcapture.mdandcomments.mdin this skill folder and followcapture.md(no branch, no hand-off). With no<N>, it infers the number from the branch after asking.fix— create a new general-fixes GitHub issue (a fresh one every time) and use it.label:<L>— hard filter: only open issues carrying label<L>(case-insensitive). Empty → stop (“no open issues with label<L>”). Ask the user to choose, even with a single match. Batch twin:/iflow-run cycle label:<L>.- a hint (milestone / topic) — soft-biases the ranking; only the
label:token filters. noplan— skip theauto_planchain for this run (ask before/iflow-planeven whenauto_planis 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 the project root first
Before any git, gh, or .issueflows/ operation, settle <project_root> and <owner/repo>, stopping at the first unambiguous answer: explicit root:<path> / repo:<name> hints; issue-flow agent resolve [--json]; the one workspace repo on a ^\d+- branch; the one .issueflows/ scaffold in view; the issueflow-workspace.toml default (say you used it). Still ambiguous → stop and ask. Then use git -C <project_root> (or issue-flow agent … -C <project_root>) and pass --repo <owner/repo> to every gh call (gh repo view takes the repo positionally).
What ships with it
2 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 Changed · -34 lines · +12 tokens per session fd8735507bad
- 1mo ago Changed · +17 lines 868d0f58ed64
- 1mo ago Changed · +2 lines 1d353af61af2
- 1mo ago Changed · +1 lines b99c5f0c501d
- 1mo ago Changed · +9 lines aa0aa0437a13
- 1mo ago Changed · +6 lines 1c628f4362d0
- 1mo ago Changed · +1 tokens per session f7dd41149f06
- 2mo ago First seen · 120 lines · 25 tokens per session scan A ae2c51a3355e
iflow-pick is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 2,326 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-31.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…