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-setup/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-setup)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-setup"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-setup/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-setup"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-setup.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.00052 | $0.01937 |
| Opus 5.5 | $0.00021 | $0.00775 |
| Sonnet 5.5 | $0.00010 | $0.00387 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade C, and why
iflow-setup scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| `uv` | **Print** the install command (`curl -LsSf https://astral.sh/uv/install.sh \| sh`, or `winget install --id=astral-sh.uv -e` on Windows) and **stop** — you cannot install a package manager for the user. Ask them Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `uv` | **Print** the install command (`curl -LsSf https://astral.sh/uv/install.sh \| sh`, or `winget install --id=astral-sh.uv -e` on Windows) and **stop** — you cannot install a package manager for the user. Ask them How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — guided project setup (/iflow-setup)
Follow this skill to get a project ready to use issue-flow — for someone who may never have driven an agentic workflow before.
It covers both entry paths from a standing start:
- New project — an empty (or nearly empty) folder that needs a Python project, a git repo, and a GitHub remote.
- Existing project — real code already, but some piece is missing (no remote,
ghnot authenticated, no issue-flow scaffold).
This is not the issue-capture step; that is /iflow-pick.
Harness mode. When the input is harness, or the user only wants to scaffold / refresh issue-flow (issue-flow init / update / workspace bootstrap, including from a parent folder of repos), read harness.md in this skill folder and follow it instead of the steps below.
Invoke: type iflow setup in chat, or /iflow-setup from the slash menu (iflow-setup 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).
Input
- (nothing) — inspect the current directory and guide from there.
new— treat this as a brand-new project (skip the new-vs-existing question).existing— treat this as an existing project.check— report readiness only; change nothing, run nothing, ask nothing.harness— scaffold / refresh only (harness.md).
What ships with it
1 file 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 · -12 lines · +13 tokens per session f0149832868f
- 1mo ago Changed e40b74213aee
- 1mo ago First seen · 118 lines · 39 tokens per session scan C 080713087c2a
iflow-setup is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 52 tokens to every session and 1,937 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-06.
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)…