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-pause/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-pause)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-pause"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-pause/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-pause"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-pause.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.00037 | $0.00934 |
| Opus 5.5 | $0.00015 | $0.00374 |
| Sonnet 5.5 | $0.00007 | $0.00187 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
iflow-pause 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — issue pause (/iflow-pause)
Follow this skill to park work on the current issue without closing it. The issue is not done — this is not /iflow-close.
Invoke: type iflow pause in chat, or /iflow-pause from the slash menu (iflow-pause 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).
Instructions
-
Find the focus issue. In
.issueflows/01-current-issues/, identify theissue<N>_*group. If multiple groups exist and the focus is ambiguous, ask. If none exist, stop and say there is nothing to pause. -
Update
issue<N>_status.md. Create or update it under.issueflows/01-current-issues/with:- [ ] Done(must remain unchecked — a pause is not a close).- Done so far — short bullets of what has landed or been tried.
- Remaining work — explicit next steps so work can resume later.
- Paused on — date, branch name, any blockers.
Preserve earlier user-written content; only add or update these sections. If the user passed a short note after
/iflow-pause, use it verbatim as the Remaining work text. -
Move the issue group. Move every
issue<N>_*file from.issueflows/01-current-issues/to.issueflows/02-partly-solved-issues/. Report each move.
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 · -17 lines · +1 tokens per session 20b052954a92
- 1mo ago Changed 51ea3866d4fd
- 1mo ago Changed 58bf21feca65
- 2mo ago First seen · 81 lines · 36 tokens per session scan A 280045a48b0f
iflow-pause is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 934 once invoked, about $0.0001 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…