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 skills add gmickel/flow-next --skill flow-next-resolve-prgit 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/skills/gmickel/flow-next/flow-next-resolve-pr)<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-resolve-pr"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-resolve-pr.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 77 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00036 | $0.01585 |
| Opus 5 | $0.00018 | $0.00792 |
| Sonnet 5 | $0.00007 | $0.00317 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
flow-next-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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Feedback Resolver
Read workflow.md for full phase-by-phase execution. Read cluster-analysis.md for cross-invocation clustering rules.
Coordinate resolution of unresolved GitHub PR review threads, top-level PR comments, and review-submission bodies. Dispatch per-thread resolver agents (parallel on Claude Code and Codex 0.102.0+, serial on Copilot/Droid), validate combined state, commit fixes, reply and resolve via GraphQL.
Role: PR feedback resolution coordinator (NOT the resolver — you dispatch the pr-comment-resolver agent per thread/cluster).
CRITICAL: flowctl is BUNDLED — NOT installed globally. which flowctl will fail (expected). The resolver scripts are bundled alongside the skill:
FLOWCTL="${CODEX_HOME:-$HOME/.codex}/scripts/flowctl"
[ -x "$FLOWCTL" ] || FLOWCTL="<plugin-root>/scripts/flowctl" # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
[ -x "$FLOWCTL" ] || FLOWCTL=".flow/bin/flowctl"
SCRIPTS="${CODEX_HOME:-$HOME/.codex}/skills/flow-next-resolve-pr/scripts"
gh CLI must be authenticated (gh auth status). jq must be on PATH.
Input
Arguments: $ARGUMENTS
Format: [PR number | PR URL | comment URL | blank] [--dry-run] [--no-cluster] [mode:autonomous]
- Blank → detect PR from current branch (
gh pr view --json number). - PR number / PR URL → full mode on that PR: handle all unresolved feedback.
- Comment URL → targeted mode: resolve only the single thread containing that comment.
--dry-run→ fetch + plan + print, no edits / commits / replies.--no-cluster→ skip cross-invocation cluster analysis (Phase 3).mode:autonomous→ question-suppression only (also derived fromFLOW_AUTONOMOUS=1env): the Phase 10 needs-human surface emitsNEEDS_HUMAN:report lines instead of blocking, threads stay open, and the run ends with the machine-readableRESOLVE_PR_VERDICT=terminal line. SetsAUTONOMOUS=1only — neverRALPH, no receipt paths. All other phases identical.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 95 lines · 36 tokens per session scan A c0bc66bdc9b9
flow-next-resolve-pr is a skill published in the GitHub repository gmickel/flow-next (691 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,585 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-30.
Other skills, from other repositories
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
st-lint
Smalltalk best-practices linter for Tonel files. Use when validating .st files before importing to the Smalltalk image (Pharo or Squeak), checking code quality after editing, or diagnosing style issues in a package.
review-workflow-activity
This skill reviews Dapr Workflow activity implementations for idempotency, retries, error boundaries, and convention violations. Use this skill when the user asks to "review workflow activities", "check activity idempotency", "audit Dapr activities", or similar.
review-workflow-management
This skill reviews the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) that an app exposes for Dapr Workflows. Use this skill when the user asks to "review workflow management", "audit workflow management API", "check workflow HTTP endpoints", or similar.
polish
Polish a completed code change with a bounded independent review protocol. Use after implementation and before final approval or PR to review intent, acceptance criteria, non-goals, diff, relevant files, verification, and previously rejected findings.
gate-check
Final quality gate before reporting task completion (Gate 3). Fills confidence assessment, runs supplementary verification for <95% items, completes self-check checklist. Writes PASS/FAIL result to subtask.md, then calls autoworker:dispatch for routing.