Borrowing it
Nothing to install: this file belongs to ffroliva/gflow-cli. 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/ffroliva/gflow-cli/develop/.claude/commands/gflow/issue-resolve.mdgit clone --depth 1 https://github.com/ffroliva/gflow-cliWrote 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/commands/ffroliva/gflow-cli/issue-resolve)<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/issue-resolve"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/issue-resolve/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ffroliva/gflow-cli/issue-resolve"><img src="https://agentmods.dev/badge/commands/ffroliva/gflow-cli/issue-resolve.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.00410 |
| Opus 5.5 | $0.00036 | $0.00164 |
| Sonnet 5.5 | $0.00018 | $0.00082 |
| Haiku 4.5 | $0.00009 | $0.00041 |
Grade A, and why
issue-resolve 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 1mo 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.
What it actually says
/gflow:issue-resolve [issue number]
Read skills/issue-resolve/SKILL.md and follow its protocol now, passing $ARGUMENTS as the issue to resolve.
Do not call
Skill(skill="issue-resolve")— the repo'sskills/*/SKILL.mdfiles are plain Markdown, not Skill-tool-invocable (only.claude/commands/gflow/*are). Read the file directly instead.
Preconditions (from /gflow:issue-assessment): verdict ∈ {CONFIRMED-BUG, LIKELY-BUG}, scope single-surface, and the fix is verifiable in this environment (or the gap is carried into the PR as "needs human e2e"). The skill isolates a bugfix/ worktree off develop, gates high-stakes changes through /gflow:predict + /gflow:scenario, fixes test-first (Opus plans → Sonnet codes → Opus reviews for non-trivial work), runs /gflow:check, opens a draft PR with a Verification-status section, runs /gflow:pr-council-review, and stops for a human to promote and merge.
Chain: /gflow:issue-assessment <N> → (if scope clear) /gflow:issue-resolve <N> → human promotes draft → human runs any headed/e2e check → merge.
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.
- 1mo ago First seen · 19 lines · 90 tokens per session scan A c506db2e6761
issue-resolve is a command published in the GitHub repository ffroliva/gflow-cli (337 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 410 once invoked, about $0.0004 per session on Opus 5.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-30.
Other commands, from other repositories
fix-issue
Diagnose and fix a reported bug, with the evidence bar the PR checklist expects.
hatch3r-codebase-map
Reverse-engineer a brownfield codebase into current-state module boundaries, integration-point inventory, tech-debt register, and dependency graph via static analysis.
hatch3r-debug
Standalone debug-and-fix workflow — add strategic debug logging, collect runtime logs from the user, perform root cause analysis, implement the fix, and clean up all debug artifacts.
hatch3r-bug-plan
Diagnose a complex incident -- reproduce the symptom, rank root-cause hypotheses, design the fix path, and emit regression coverage items as a board-ready investigation.
hatch3r-quick-change
Lightweight workflow for small changes not tracked on the board: adaptive ceremony, inline or sub-agent implementation, batch support.
hatch3r-bug-pipeline
Run a known-cause bug fix through a 3-phase test-first pipeline -- reproduce + root-cause, regression-test + fix together, then root-cause-depth review -- with full sub-agent delegation.