Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/jepegit/issue-flow/iflow-plannpx skills add jepegit/issue-flow --skill iflow-plangit 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-plan)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-plan"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-plan.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 | $0.00025 | $0.01963 |
| Opus 5 | $0.00013 | $0.00981 |
| Sonnet 5 | $0.00005 | $0.00393 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
iflow-plan 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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — issue plan (/iflow-plan)
Follow this skill to design the approach for the focus issue before touching code, and to get the plan confirmed ahead of /iflow-build.
Invoke: type iflow plan in chat, or /iflow-plan from the slash menu (iflow-plan 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.
After resolution, treat the result as <project_root> and <owner/repo>:
- Git:
git -C <project_root> …(orissue-flow agent … -C <project_root>for supported ops). - GitHub: pass an explicit repo on every
ghcall — never rely ongh's implicit cwd default. For most commands use--repo <owner/repo>; exception:gh repo viewtakes the repo as a positional arg (gh repo view <owner/repo> …) and rejects--repo. - Paths: all
.issueflows/…paths are under<project_root>.
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.
- 3d ago First seen · 114 lines · 25 tokens per session scan A fc5f7033ab3a
iflow-plan is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 21d ago), licensed MIT. It adds 25 tokens to every session and 1,963 once invoked, about $0.0001 per session on Opus 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.