flow-next-impl-review

flow-next-impl-review is a skill for Claude Code, Codex from gmickel/flow-next. It costs 34 tokens per session (2,184 once invoked), scanned A, original, MIT.

A process for reviewing code changes in a flow-next project, using the configured review system.

In plain words
What is it for?
Use it to review a current diff, optionally run deeper validation, and produce findings based on the selected review backend.
Why use it?
It helps find correctness, design, and implementation problems in a branch before the changes are accepted.

Skill for Claude CodeCodex

Written for Claude Code and Codex: user-invocable in frontmatter, but also agents/openai.yaml present. Also seen: mentions Codex.

Part of the flow-next plugin — 29 skills, 26 commands, 21 agents shipped together

Good fit Use it to review a current diff, optionally run deeper validation, and produce findings based on the selected review backend.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gmickel/flow-next/flow-next-impl-review
Install

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.

Any agent
npx skills add gmickel/flow-next --skill flow-next-impl-review
Clone the repo
git clone --depth 1 https://github.com/gmickel/flow-next

Made for: Claude Code, Codex.

Or install flow-next, the plugin that ships this one along with the rest of its 29 skills, 26 commands, 21 agents.

Wrote 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.

agentmods badge for flow-next-impl-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-impl-review/github.svg)](https://agentmods.dev/skills/gmickel/flow-next/flow-next-impl-review)
Your own site
<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-impl-review"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-impl-review/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.

agentmods 80×15 button for flow-next-impl-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-impl-review"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-impl-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,184 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

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 →

  • medium Excessive Agency · line 81
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.02184
Opus 5.5 $0.00014 $0.00874
Sonnet 5.5 $0.00007 $0.00437
Haiku 4.5 $0.00003 $0.00218

Measured 11d ago against content hash d57dc294072d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flow-next-impl-review 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 11d 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.

plugins/flow-next/codex/skills/flow-next-impl-review/SKILL.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation review

You coordinate; the configured backend reviews. Never author a verdict yourself, and use one backend for the whole review. Read working-rules.md first: its Review section decides which findings you fix.

Arguments: [task id] [--base <commit>] [--review=<backend>] [--deep[=passes]] [--validate] [--interactive] [--no-triage] [focus areas]. Without --base the whole branch is reviewed against main. A spec or branch review passes no id.

1. Setup

One Bash call; fill the three literals from the arguments.

set -e
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"
REVIEW_ID="<task id, or empty for a spec or branch review>"
BACKEND="<value of --review, or empty>"
DIFF_BASE="<value of --base, or empty>"
[ -n "$BACKEND" ] || BACKEND=$("$FLOWCTL" review-backend "$REVIEW_ID")
[ -n "$DIFF_BASE" ] || { DIFF_BASE=main; git rev-parse -q --verify main >/dev/null || DIFF_BASE=master; }
echo "FLOWCTL=$FLOWCTL BACKEND=$BACKEND DIFF_BASE=$DIFF_BASE"
git diff --shortstat "$DIFF_BASE"...HEAD
  • ASK: stop; no backend is configured (/flow-next:setup, or pass --review=<backend>).
  • none: no review; say so.
  • rp or export: removed; tell the user in one line "RepoPrompt review (rp, export) was removed in flow-next 8.0.0; review backends: claude, codex, copilot, cursor, host." and stop as for ASK.
  • host, any of --deep, --validate, --interactive, --no-triage, FLOW_VALIDATE_REVIEW=1 or FLOW_REVIEW_DEEP=1 in the environment, or an instruction about the reviewers ("one reviewer", "three model families"): read other-paths.md and follow it and the backend's workflow file to the end. That file owns the verdict, fix and re-review handling; of step 4, only the OVERRIDDEN: line ending an unattended loop applies, never its fix pass or re-review.
  • claude when a Claude model wrote the change: say once that this review is same-family, then continue.

Read the full file on GitHub · 135 lines

Changes

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.

  1. 11d ago Changed · +1 lines d57dc294072d
  2. 16d ago Changed · +10 lines 5e308ae485fa
  3. 18d ago Changed · -12 lines 1b346852951e
  4. 20d ago Changed · -152 lines 6653fc13d567
  5. 25d ago Changed · +3 lines d8d77c7f5c87
  6. 1mo ago Changed c325050864a2
  7. 1mo ago Changed · +2 lines ced150cc2ba8
  8. 1mo ago Changed 4e8ebe2db30a
  9. 1mo ago Changed · +27 lines 19ee47a662aa
  10. 1mo ago First seen · 256 lines · 34 tokens per session scan A 0c2f20d36a7d

Subscribe to this mod's changes

flow-next-impl-review is a skill published in the GitHub repository gmickel/flow-next (713 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 2,184 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-08-30.

Related

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.

umputun/cc-thingz · 51 tokens

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.

mumez/smalltalk-dev-plugin · 52 tokens

review-pubsub-subscriptions

Reviews Dapr pub/sub subscriptions and handlers in .NET and Python (declarative, programmatic, streaming) for CloudEvent handling, response statuses, idempotency, dead-letter handling and duplicate subscriptions. Use for "review my Dapr subscribers" or "check pub/sub handlers for idempotency".

diagrid-labs/dapr-skills · 69 tokens

review-workflow-management

Read-only audit of the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) an app exposes for Dapr Workflows, with DWF-MGT-NNN findings. Use for "review workflow management" or "check workflow HTTP endpoints". To operate runs on Diagrid Catalyst use the catalyst-ai plugin.

diagrid-labs/dapr-skills · 74 tokens

review-pubsub-components

Reviews Dapr pub/sub configuration (components, Subscription files, resiliency, dapr.yaml and Aspire wiring) for inline secrets, unsecured brokers, dead-letter topics without retry policies, scopes and app-id or port collisions. Use for "review my pub/sub components" or "audit Dapr pubsub YAML".

diagrid-labs/dapr-skills · 68 tokens

review-pubsub-publishing

Reviews Dapr pub/sub publishing code in .NET and Python for swallowed publish failures, wrong pub/sub names, content types, client lifetime, bulk-publish partial failures and payload size. Use for "review my pub/sub publishing code" or "audit Dapr publish calls".

diagrid-labs/dapr-skills · 62 tokens