issue-flow: Skill for Claude Code

.cursor/skills/iflow-cleanup/SKILL.md

iflow-cleanup is a skill for Claude Code, Cursor from jepegit/issue-flow. It costs 78 tokens per session (2,555 once invoked), scanned A, original, MIT.

A post-merge Git workflow for returning to the default branch and cleaning up local branches that have already been merged. Git is a system for tracking code changes between branches.

In plain words
What is it for?
Switching back after a merge, deleting merged local branches, and optionally checking the GitHub remote for branch cleanup.
Why use it?
It removes finished local branches in a controlled way after a pull request has been merged, while avoiding forced deletion.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: disable-model-invocation in frontmatter, but also installed under .cursor/.

This is jepegit/issue-flow's own configuration. It tells Claude Code and Cursor how to work on issue-flow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything issue-flow configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jepegit/issue-flow/main/.cursor/skills/iflow-cleanup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jepegit/issue-flow

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for iflow-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-cleanup/github.svg)](https://agentmods.dev/skills/jepegit/issue-flow/iflow-cleanup)
Your own site
<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-cleanup"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-cleanup/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.

agentmods 80×15 button for iflow-cleanup

Your own site · 80×15
<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-cleanup"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,555 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.02555
Opus 5.5 $0.00031 $0.01022
Sonnet 5.5 $0.00016 $0.00511
Haiku 4.5 $0.00008 $0.00255

Measured 8d ago against content hash 769eb4a217cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

iflow-cleanup 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.

.cursor/skills/iflow-cleanup/SKILL.md · 106 lines

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 — cleanup (/iflow-cleanup)

Post-merge branch hygiene after a PR has landed.

Invoke: type iflow cleanup in chat, or /iflow-cleanup from the slash menu (iflow-cleanup 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

Trailing text Effect
nothing Phase A: the current branch's PR plus every other local branch already landed on the default.
a branch name Phase A targets that branch instead of the current one.
include github / with github / github Also run Phase B, the remote audit (github.md). no github / local only skips it.
self-update / bleeding edge Upgrade the tool after a successful pull. skip self-update / no bleeding skips it.
ask a1 / ask a2 Force that phase's prompt even when its cleanup_yes_* knob is on.
drive / landed Orchestrator token from /iflow-run drive: its earlier confirm already covered -D on landed branches, so A1/A2 run without re-asking. A2 narrows to squash_landed, plus merged_pr_divergent with no commit newer than the PR's mergedAt; never unique_work / skipped. A human never passes it.
all / workspace Every scaffolded workspace member (step 4b, workspace.md). At most three confirms in total (A1, A2, Phase B).
prs Refresh open PRs that went DIRTY after another merge: read prs.md instead of the steps below.
archive Condense old solved issue groups: read archive.md instead of the steps below.

Read the full file on GitHub · 106 lines

Files

What ships with it

5 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.

Changes

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.

  1. 8d ago Changed · -75 lines · +12 tokens per session 769eb4a217cd
  2. 1mo ago Changed · +36 lines 4afdca92f9d1
  3. 1mo ago Changed 425c251d4841
  4. 1mo ago Changed · +1 lines dde01cd4a6af
  5. 1mo ago Changed · +15 lines cdaefc6b6a83
  6. 1mo ago Changed · +1 lines 02633bbf298f
  7. 1mo ago Changed · +20 lines · +14 tokens per session 61f704f32740
  8. 1mo ago Changed · +4 lines · +7 tokens per session 617bb2da8760
  9. 2mo ago First seen · 104 lines · 45 tokens per session scan A 207d4556156b

Subscribe to this mod's changes

iflow-cleanup is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 78 tokens to every session and 2,555 once invoked, about $0.0003 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.