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-autonpx skills add jepegit/issue-flow --skill iflow-autogit 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.00037 | $0.02483 |
| Opus 5 | $0.00018 | $0.01241 |
| Sonnet 5 | $0.00007 | $0.00497 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
iflow-auto 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-flow — advanced auto (/iflow-auto)
Follow this skill to run an unattended large-change flow over a confirmed
epic: select a stage, drive it through /iflow-cycle, record durable state in
auto_status.md, run adversarial inter-epoch review (review), then honour
the adversarial loop budget (re-queue or stop-and-ask).
Contract: .issueflows/04-designs-and-guides/advanced-auto-mode.md
(criteria table, budget, outcomes).
Input
<N>— epic anchor issue number (requiresepic<N>_plan.mdwithStatus: confirmed).stage <k>— optional stage index; default = earliest unfinished published stage (issue-flow agent epic-status <N> --json→current_stage).loops:<n>— override adversarial loop budget for this run (baked default 2 from[issueflow].auto_adversarial_loops).review— run only the adversarial procedure for epic<N>(and optionalstage <k>); skip cycle unless a full auto run is also intended.status— printauto_status.md/ epic-status and stop (no confirm).dry-run— resolve stage + queue, show what would run, stop (no confirm).
Invoke: type iflow auto in chat, or /iflow-auto from the slash menu (iflow-auto 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.
- 2d ago First seen · 181 lines · 37 tokens per session scan A 5208ec9c5435
iflow-auto is a skill published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 2,483 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.
smithers-supervise
Watch for stale running runs and auto-resume them. Run smithers supervise --help for usage details.