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-issue/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-issue)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-issue"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-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.
<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-issue"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-issue.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.00061 | $0.00770 |
| Opus 5.5 | $0.00024 | $0.00308 |
| Sonnet 5.5 | $0.00012 | $0.00154 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
iflow-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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — issues (/iflow-issue)
Create or reshape GitHub issues. Every mode shows what it will create or change and asks before writing to GitHub.
Invoke: type iflow issue in chat, or /iflow-issue from the slash menu (iflow-issue 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).
Pick the mode
The first word after issue selects the mode. Read only that mode's file in this skill folder and follow it. Forward the remaining text verbatim.
| Input | Mode file | What it does |
|---|---|---|
| free text, or nothing | new.md |
Draft and create one well-specified issue (context / spec / acceptance criteria), then optionally branch and capture it. |
fix [<N>] |
fix.md |
Interactive iterative-fixes session: one issue + long-lived branch, many small confirmed fixes, ends with /iflow-close. |
epic <N> / epic <N> publish [stage <k>] / epic start [N] / epic stop |
epic.md |
Plan a change too large for one issue as staged sub-issues; publish a stage; start or stop a one-and-ask epic session. |
epic <free text> |
new.md (epic-anchor mode) |
Create the epic anchor issue first, then offer epic <N>. |
split <N> |
split.md |
Cut one over-large existing issue into 2–5 flat GitHub sub-issues. |
review |
review.md |
Review open issues and apply labels (v1: the yolo label). |
What ships with it
5 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 · -70 lines · +31 tokens per session 2a0ed102295b
- 1mo ago Changed · +17 lines 2760a68a0d54
- 1mo ago Changed · +2 lines a90768a84981
- 1mo ago Changed · +1 lines 28eaaffd4f8d
- 1mo ago Changed · +8 lines 1695509afc95
- 1mo ago Changed · +1 tokens per session 412f8e3ef6ee
- 2mo ago First seen · 101 lines · 29 tokens per session scan A 5e5820549506
iflow-issue is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 770 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)…