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-close/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-close)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-close"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-close/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-close"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-close.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.00045 | $0.02487 |
| Opus 5.5 | $0.00018 | $0.00995 |
| Sonnet 5.5 | $0.00009 | $0.00497 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
iflow-close 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — close (/iflow-close)
Finish and land the focus issue: tests, optional version bump, tracking updates, commit, push, PR. Branch deletion belongs to /iflow-cleanup.
Invoke: type iflow close in chat, or /iflow-close from the slash menu (iflow-close also works).
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).
Input tokens
| Token | Effect |
|---|---|
bump / patch / minor / major / stable / alpha / beta / rc / post / dev |
Version bump (step 2). Natural language works too; ask once if unclear; use major only when the user names it. |
nohistory / skip history |
Skip the changelog trailers (step 3). |
log "..." / note "..." |
Use this text as the changelog bullet. |
stay / stay on branch / don't switch |
Stay on the issue branch after the PR step. |
draft |
Open or keep a draft PR; skips the yolo merge. |
yolo |
Hands-off: decide the changelog without asking, merge the PR, switch back and pull. Used by /iflow-run yolo. |
ops / nopr / no-pr |
No PR. Read ops.md in this skill folder and follow it instead of the steps below. Cannot combine with yolo or draft; stop and ask if combined. |
What ships with it
6 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 · -87 lines · +18 tokens per session 75b5f4c61aa1
- 1mo ago Changed · +20 lines 0c5cf08f48f2
- 1mo ago Changed · +17 lines e5c11ae541a4
- 1mo ago Changed · +22 lines 62768ab32b68
- 1mo ago Changed · +21 lines af32476832cd
- 1mo ago Changed 7939161f3a33
- 1mo ago Changed · +20 lines 8257a26dfe20
- 1mo ago Changed 57a211d7cfd1
- 1mo ago Changed · +5 lines 7854ec34041e
- 2mo ago First seen · 129 lines · 27 tokens per session scan A d6384be3ee7f
iflow-close is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 2,487 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
gsd-quick-batch
Batch several /skill:gsd-quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-pause-work
Create context handoff when pausing work mid-phase.
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.
gait-session-tracking
GAIT session lifecycle management - branch creation, turn recording, audit logging for every NetClaw operation. Use when starting a new NetClaw session, recording a health check or config change, pinning a pre-change baseline, or viewing the audit trail for a troubleshooting session.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.