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 commands/ffroliva/gflow-cli/issue-resolvegit clone --depth 1 https://github.com/ffroliva/gflow-cliWhat 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.00090 | $0.00410 |
| Opus 5 | $0.00045 | $0.00205 |
| Sonnet 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 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.
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.
- 2d 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 (136 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 410 once invoked, about $0.0005 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-30.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
translation-review
全面审核翻译质量: 对比原版、专项检查、质量评分与发布验证, 发现问题时自动衔接修复流程.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
03-gap
Translate the visibility baseline + brand context into a ranked list of content actions that should move the needle. Identifies absent queries, contested queries, and competitor-displacement opportunities. Outputs contentpriorities.json validated against schema. Use after 02-audit; consumed by 04-content-brief.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.