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.
git clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/gmickel/flow-next/resolve-pr)<a href="https://agentmods.dev/commands/gmickel/flow-next/resolve-pr"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/resolve-pr/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/gmickel/flow-next/resolve-pr"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/resolve-pr.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.00026 | $0.00145 |
| Opus 5.5 | $0.00010 | $0.00058 |
| Sonnet 5.5 | $0.00005 | $0.00029 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
resolve-pr 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 23d 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
IMPORTANT: This command MUST invoke the skill flow-next-resolve-pr
The ONLY purpose of this command is to call the flow-next-resolve-pr skill. You MUST use that skill now.
Arguments: $ARGUMENTS
Pass the arguments to the skill. The skill handles fetch, triage, dispatch, validate, commit, reply, and resolve.
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.
- 23d ago Changed · +1 lines af0855f3068d
- 1mo ago First seen · 14 lines · 26 tokens per session scan A 3052fd15c1da
resolve-pr is a command published in the GitHub repository gmickel/flow-next (711 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 145 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
code-review
Review someone else's open GitHub PR — posts a real review with line-anchored inline comments; verdict computed mechanically; mandatory preview gate. Workspace-aware. For your OWN working diff, prefer the bundled /code-review instead.
address
Answer reviewer comments on YOUR open PR — categorize unresolved threads, push fixes, and post replies. Workspace-aware across linked PRs.
check-pr
Check a PR's CI status, reviews, comments, and merge readiness.
cut-release
Prepare a release — bump the version, finalize the changelog, and open the release PR that publishes on merge.
pre-pr-check
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.