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-version-bumpnpx skills add jepegit/issue-flow --skill iflow-version-bumpgit 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.00034 | $0.01780 |
| Opus 5 | $0.00017 | $0.00890 |
| Sonnet 5 | $0.00007 | $0.00356 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
iflow-version-bump 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — version bump
Use this skill to bump the project version before landing work (often invoked from /iflow-close) — either at a specific level, or with the default rule below when none is given. What "bump" means depends on the release strategy, so resolve that first.
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.
CLI fast path (optional). If the
issue-flowCLI is onPATH, runissue-flow agent version-plan [--bump <level>] --json. It detects the strategy frompyproject.toml, reads the latest tag, does the PEP 440 next-version arithmetic, and returns the exact commands — read-only, it never edits files or creates tags. Thethis-project.mdrelease section still wins over its detection: when the payload saysbrief_release_section: "filled", read the section and follow it. If the CLI is missing or errors, fall back to the manual steps below.
Resolve the release strategy first
In order — stop at the first that answers:
.issueflows/04-designs-and-guides/this-project.md— if its "Release & version bump" section is filled in, follow it verbatim. It is the project's own documentation and beats every default below.- Detect from
pyproject.toml:dynamic = ["version"]under[project], together with a tag-driven backend ([tool.setuptools_scm],hatch-vcsin the build requires,versioningit, or similar) → git-tag derived strategy.- a static
version = "..."under[project]→ static version (uv) strategy.
- Neither (no
pyproject.toml, or no version at all) → skip the bump, explain why, and continue the rest of the flow (for example/iflow-close) without failing.
Record what you learn (self-healing). When the strategy came from detection or from the user explaining it — i.e. not from this-project.md — add or fill in the "Release & version bump" section of .issueflows/04-designs-and-guides/this-project.md with a short description of the strategy and the exact commands, so no future session has to rediscover it. The brief is user-owned and never overwritten by issue-flow update, so the note is durable.
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 · 117 lines · 34 tokens per session scan A 27089e016337
iflow-version-bump is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 19d ago), licensed MIT. It adds 34 tokens to every session and 1,780 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.