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.svg" alt="Measured on agentmods" 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.00039 | $0.02187 |
| Opus 5 | $0.00019 | $0.01094 |
| Sonnet 5 | $0.00008 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00219 |
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 today.
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 — 118 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. Capturing a GitHub issue into .issueflows/01-current-issues/ is /iflow-capture; picking what to work on is /iflow-pick. /iflow-init only cold-starts the harness.
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 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), orrepo:owner/name. - CLI fast path —
issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returnedproject_rootandrepo; pass-C <project_root>to otherissue-flow agent …subcommands. When the answer came from the workspace registry, the payload setsresolved_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.tomlat the workspace root (created withissue-flow workspace init) may name adefaultmember repo; use it when no scaffold matched above. Tell the user the default was used. - Ambiguous → stop and ask; never guess between sibling repos.
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.
- today 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 yesterday), licensed MIT. It adds 39 tokens to every session and 2,187 once invoked, about $0.0002 per session on Opus 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
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.
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 stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…