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-reviewnpx skills add jepegit/issue-flow --skill iflow-reviewgit 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-review)<a href="https://agentmods.dev/skills/jepegit/issue-flow/iflow-review"><img src="https://agentmods.dev/badge/skills/jepegit/issue-flow/iflow-review.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.00023 | $0.01819 |
| Opus 5 | $0.00012 | $0.00910 |
| Sonnet 5 | $0.00005 | $0.00364 |
| Haiku 4.5 | $0.00002 | $0.00182 |
Grade A, and why
iflow-review 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 5d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — review and label issues (/iflow-review)
Follow this skill to review open GitHub issues and apply labels. It is
extendable by review kind; v1 supports yolo only (apply the configured
yolo label to issues that pass the yolo-fitness judgment).
Do not auto-dispatch from /iflow, /iflow-build, or /iflow-close. Off-path
only. Do not create new GitHub issues here (use /iflow-issue,
/iflow-pick fix, or /iflow-epic … publish). Do not remove labels in v1.
Invoke: type iflow review in chat, or /iflow-review from the slash menu (iflow-review 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.
Resolve project root (multi-root workspaces)
Before any git, gh, or .issueflows/ path operation in this workflow:
Resolution order (stop when unambiguous):
- Explicit hints in slash input —
root:<path>,repo:<folder-basename>(directory name, e.g.cellpy-core), orrepo:owner/name. - CLI fast path —
issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returnedproject_rootandrepo; pass-C <project_root>to otherissue-flow agent …subcommands. When the answer came from the workspace registry, the payload setsresolved_via_workspace_default: true. - Branch context — exactly one workspace repo whose branch matches
^\d+-→ that root. - Single scaffold — exactly one
.issueflows/tree visible in the workspace → that root. - Workspace default — an
issueflow-workspace.tomlat the workspace root (created withissue-flow workspace init) may name adefaultmember repo; use it when no scaffold matched above. Tell the user the default was used. - Ambiguous → stop and ask; never guess between sibling repos.
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.
- 5d ago First seen · 139 lines · 23 tokens per session scan A 593f72af0400
iflow-review is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,819 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…