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-archivenpx skills add jepegit/issue-flow --skill iflow-archivegit 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-archive)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-archive"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-archive.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 | $0.00029 | $0.01271 |
| Opus 5 | $0.00015 | $0.00635 |
| Sonnet 5 | $0.00006 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
iflow-archive 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — archive solved issues (/iflow-archive)
Follow this skill to shrink the solved-issues archive:
old issue<N>_* groups under .issueflows/03-solved-issues/ are
summarised into one dated markdown file and the originals are deleted (they
stay recoverable through git history).
Do not use this to park or close an active issue — that is /iflow-pause / /iflow-close. This skill only touches .issueflows/03-solved-issues/.
Input
- (nothing) — smart default: propose archiving every solved group except the 5 most recent (highest issue numbers).
keep <K>— same, but keep the<K>most recent groups instead.- an explicit list (e.g.
12 13 24) — archive exactly those issues. all— archive every solved group.
Invoke: type iflow archive in chat, or /iflow-archive from the slash menu (iflow-archive also works).
MODEL & EXECUTION DIRECTIVE
Profile: reasoning — Prioritize deep thinking and careful trade-offs over speed or token economy.
In Cursor: switch to a thinking-capable model before invoking this step (not Auto-only).
Keep scope tight to what this step requires.
Instructions
CLI fast path (optional). If the
issue-flowCLI is onPATH, the mechanical deletion step has a deterministic shortcut:issue-flow agent archive <N> [<N> ...](add--dry-runto preview,--jsonfor a machine-readable object). It removes the chosen groups' files and reports the pre-archive HEAD sha — you still select candidates, confirm with the user, and write the summary file yourself. The CLI is optional: if it is missing or errors, fall back to the manual instructions below.
-
Preflight. Require a clean working tree (
git status --porcelain); if dirty, stop and ask the user to commit or stash first — the recovery ref is only meaningful when the deletion lands as its own commit. Capture the pre-archive ref:git rev-parse HEAD. -
Select candidates. List every
issue<N>_*group in.issueflows/03-solved-issues/with its number and title (from the# Issue #N: <title>heading ofissue<N>_original.md). Apply the input rule (default: all except the 5 most recent by issue number). Show the resulting candidate list — number, title, file names — and let the user add/remove issues.
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.
- 3d ago First seen · 93 lines · 29 tokens per session scan A f67ff91e5329
iflow-archive is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 1,271 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
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…