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-closenpx skills add jepegit/issue-flow --skill iflow-closegit clone --depth 1 https://github.com/jepegit/issue-flowWhat 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.00027 | $0.03587 |
| Opus 5 | $0.00014 | $0.01793 |
| Sonnet 5 | $0.00005 | $0.00717 |
| Haiku 4.5 | $0.00003 | $0.00359 |
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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — issue close (/iflow-close)
Follow this skill to finish and land work: tests, optional version bump, issue-folder updates, git, and PR.
Post-merge branch hygiene lives in /iflow-cleanup — this skill never deletes branches.
Optional version bump (command input)
If the user included text after /iflow-close that requests a version bump:
bump(no level) → apply the pre-release-aware default.- A named level (
patch,minor,major,stable,alpha,beta,rc,post,dev) → use exactly that. - Otherwise infer the level from natural language (e.g. "bugfix release" →
patch); ask once if ambiguous. Never auto-pickmajor.
The exact semantics and the default rule live in .cursor/skills/iflow-version-bump/SKILL.md — that skill is the source of truth. When a bump applies: read it, then run the bump from the project root after the sanity check and before issue-folder updates and before commit / push / PR.
Changelog update tokens (command input)
nohistoryorskip history→ skip step 3 entirely.log "..."ornote "..."→ override the bullet summary verbatim. Otherwise the GitHub issue title is used.
Branch switch tokens (command input)
stay,stay on branch,don't switch, ordont switch to main→ after the PR step, stay on the issue branch instead of switching back to the default branch.
Draft PR token (command input)
draft→ when creating a PR in step 8, usegh pr create --draft. If an open PR already exists, leave it draft (do not mark ready).draftskips yolo merge entirely (step 8a).
Hands-off token (command input)
yolo(used by/iflow-yolo) → close the loop without user input: write theHISTORY.mdbullet without a confirm prompt (step 3), merge the PR right after opening/updating it (step 8a), then switch back to the default branch andgit pull --ff-only(step 9, unlessstaywas also passed).
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.
- 2d 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 20d ago), licensed MIT. It adds 27 tokens to every session and 3,587 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
prepare-paperclip-pr
Prepare a Paperclip branch for PR with commits, template body, and checks.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
flow-next-work
Execute a flow-next spec or task end-to-end with worker subagents, gates, and commits. Use when asked to work on, implement, or execute fn-N.
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.
cursor-agents-workflow
Human handoff, Linear branch names, reviewable (non-draft) PRs, Claude, Greptile, and Codex review comments, preview test steps, proof of work posted on the GitHub PR, and review-doubt notes for Cursor agents. Use when a Cursor Cloud or Cursor desktop agent implements a Linear issue, opens a GitHub PR, asks a human to…