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/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)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow/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"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow.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.00041 | $0.01986 |
| Opus 5.5 | $0.00016 | $0.00794 |
| Sonnet 5.5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00199 |
Grade A, and why
iflow 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — iflow smart dispatcher (/iflow)
Run the right next step: detect state and route to /iflow-pick <N> (capture), /iflow-plan, /iflow-build, or /iflow-close, forwarding trailing args verbatim. Every other command runs only when the user types it.
Invoke: type iflow in chat, or /iflow from the slash menu.
MODEL & EXECUTION DIRECTIVE
Profile: economy — Prioritize speed and token economy over deep reasoning.
In Cursor: use Auto or a fast model before invoking this step.
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).
Instructions
CLI fast path (optional). If the
issue-flowCLI is onPATH, runissue-flow agent state --jsonto resolve the focus issue, its lifecycle stage, the suggestednext_command, and (when there is no focus)epic_hint/epic_sessionin one deterministic step (covers instructions 1–2), then dispatch — or stop for the epic gap. The CLI is optional: if it is not installed or it errors, fall back to the manual instructions below.
- Resolve the focus issue number
N.- Prefer
issue-flow agent state --jsonwhen the CLI is onPATH(fieldsfocus,next_command,epic_hint,epic_session,cli_version,skills_version,version_drift). - Version drift. If the payload reports
version_drift: true, print one warning line before anything else —skills stamped <skills_version>, CLI <cli_version> — runissue-flow update`` — and keep going with the dispatch. Stale skill text is how a newer CLI ends up driven by old instructions; the warning is the fix, not a stop. Leave runningissue-flow updateto the user. - Manual fallback:
git branch --show-current. If it matches^(\d+)-.+, the leading digits are the authoritativeN. - List
issue<n>_*groups in.issueflows/01-current-issues/, and also check.issueflows/02-partly-solved-issues/and.issueflows/03-solved-issues/for archived groups matchingN. - Pick
Nby precedence:- Branch-derived
Nwins, regardless of whether a group forNexists in01-current-issues/. State A will apply when noissue<N>_*files are present yet. Ifissue<N>_*is archived under02-partly-solved-issues/or03-solved-issues/, warn the user that capture's archived-issue guard will ask for an explicit confirmation before re-opening. - No branch-derived
N, exactly one group exists in01-current-issues/→ use it. - No branch-derived
N, no groups at all → epic gap check (step 1a), else state A. - No branch-derived
N, multiple groups → stop and ask.
- Branch-derived
- Prefer
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 · -21 lines · +4 tokens per session ee4682d3b095
- 1mo ago Changed · +1 lines 1f63049ba18b
- 1mo ago Changed 724fa5c71e28
- 1mo ago Changed · +2 lines 3ff617194519
- 1mo ago Changed 17d4e45bb28b
- 1mo ago Changed f684febc5f62
- 1mo ago Changed · +1 tokens per session 93626d4ca03a
- 2mo ago First seen · 110 lines · 36 tokens per session scan A 946b89015695
iflow is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 41 tokens to every session and 1,986 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…