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-history-update/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-history-update)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-history-update"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-history-update.svg" alt="Measured on agentmods" 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.00034 | $0.01527 |
| Opus 5 | $0.00017 | $0.00763 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
iflow-history-update 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — history update
Use this skill to update the project's changelog file (default HISTORY.md, overridable via ISSUEFLOW_HISTORY_FILE in .env) as part of /iflow-close. It never runs on its own schedule; it is driven by the "update HISTORY" step, and does not run when the user passed nohistory / skip history.
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.
Preconditions
- The changelog file (
HISTORY.md) exists at the project root. If it does not, skip this step, print "noHISTORY.md— skipping changelog update" and continue the rest of/iflow-close. Never create the file from this skill. - The file is in Keep a Changelog shape: a top-level
## [Unreleased]heading, with released versions below as## [x.y.z] - YYYY-MM-DDheadings. If the shape does not match, stop and report the mismatch instead of guessing — let the user fix the file or passnohistory.
Inputs from /iflow-close
| From | Used for |
|---|---|
Issue number N |
Reference suffix on the new bullet, e.g. (#42). |
Issue title (from .issueflows/01-current-issues/issue<N>_original.md) |
Default bullet summary. |
log "..." / note "..." input token |
Override the bullet summary verbatim. |
Version-bump outcome (from step 2 of /iflow-close) |
Decides append vs promote (see below). |
Operation modes
A. No version bump — append to [Unreleased]
-
Read
HISTORY.md. Locate the first## [Unreleased]heading. The block ends at the next## [heading (or EOF). -
Compose the new bullet:
- <summary>. (#<N>)Summary =
log "..."override if provided, else the issue title with sentence case, trailing period trimmed before the.we add. -
Append the bullet to the end of the Unreleased bullet list. Preserve existing formatting (blank lines, list markers). Do not reorder existing entries.
-
Write the change without a confirm prompt (
confirm_changelog_updateis false; same as theyolotoken's history behaviour). Still report what was written.
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 Changed · +16 lines 1b2caee8d21b
- 7d ago First seen · 94 lines · 34 tokens per session scan A 75fcc6f7aba8
iflow-history-update is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,527 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.