What is mcaf-human-review-planning?

A practical plan for reviewing a large AI-generated code change when a person cannot inspect every line. It traces real user and system flows, finds risky boundaries, and ranks the files that deserve attention first.

Use it to plan human review of a large generated code drop, prioritize files in a target area, and create a review sequence around key user or operational flows.

It reduces the time needed for manual review while focusing attention on the areas most likely to contain important defects.

How managedcode/MCPGateway configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to managedcode/MCPGateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/managedcode/MCPGateway/main/.codex/skills/mcaf-human-review-planning/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/managedcode/MCPGateway

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-human-review-planning/github.svg)](https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-human-review-planning)

Your own site

<a href="https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-human-review-planning"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-human-review-planning/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-human-review-planning"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-human-review-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,158 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.

Origin 89% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00076	$0.01158
Opus 5.5	$0.00030	$0.00463
Sonnet 5.5	$0.00015	$0.00232
Haiku 4.5	$0.00008	$0.00116

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

Security

Grade A, and why

mcaf-human-review-planning 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.

Origin

This is a copy

89% identical to dotnet-mcaf-human-review-planning — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/skills/mcaf-human-review-planning/SKILL.md · 121 lines

How it starts

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

MCAF: Human Review Planning

Trigger On

a large AI-generated code drop needs a human review plan
the reviewer cannot inspect every line and needs prioritization
the user asks which files are highest risk before doing manual review
the user names a generated folder and wants a saved review plan for it

Value

produce a concrete project delta: code, docs, config, tests, CI, or review artifact
reduce ambiguity through explicit planning, verification, and final validation skills
leave reusable project context so future tasks are faster and safer

Do Not Use For

normal small pull-request review
automated bug finding without creating a human review sequence

Inputs

the target folder, feature area, or bounded context under review
the main user journeys or operational flows involved
any known architecture context, adjacent entities, or existing system rules
any exact output path the user wants for the saved plan

Quick Start

Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

Read enough of the target area and its immediate boundaries to understand the generated code before planning review.
Map the natural flow of operations first:
- sign up or authentication
- create
- update
- register or configure
- execute primary business action
- complete, archive, or finalize
Use that flow to derive the most efficient human review sequence.
Use the reviewer's domain knowledge as a force multiplier:
- compare the generated code against known architecture and existing entities
- look for places where the new feature should behave like nearby existing flows
- prioritize boundaries where generated code may drift from established system rules
Identify high-risk review zones:
- entry points and orchestration layers
- persistence and state transitions
- cross-boundary integrations
- permissions, validation, and invariants
- side effects such as email, payments, jobs, or notifications
Produce two separate outputs:
- prioritized review flow
- prioritized files or modules to inspect
Present both outputs in chat.
If the user asks for a durable artifact, save the plan to the exact docs path they requested; otherwise use docs/AREA/HUMAN_REVIEW_PLAN.md.

Read the full file on GitHub · 121 lines

Files

What ships with it

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

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.

1mo ago First seen · 121 lines · 76 tokens per session scan A d9e627657972

Subscribe to this mod's changes

mcaf-human-review-planning is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 8d ago), licensed MIT. It adds 76 tokens to every session and 1,158 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to dotnet-mcaf-human-review-planning, differing in 25 lines, and is treated as a copy.

C# and .NET Code review ai-extensions dotnet embeddings mcp mcp-gateway

resharper-clt

Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…

managedcode/dotnet-skills · 107 tokens

roslynator

Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…

managedcode/dotnet-skills · 107 tokens

stylecop-analyzers

Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…

managedcode/dotnet-skills · 142 tokens

dotnet-best-practices

Ensure .NET/C# code follows maintainable, modern best practices. Use when reviewing or improving C# code, solution structure, async patterns, dependency injection, or testability.

PracticalSwan/agent-skills · 43 tokens

cratis-engineering-csharp-conventions

Apply the Cratis C# house conventions when writing or reviewing C# in a Cratis repository - formatting, naming, records and primary constructors, nullable handling, XML documentation, custom exceptions, structured logging, dependency injection, and service lifetimes. Use for any "how should this be written" C# style…

Cratis/AI · 86 tokens

quickdup

Use the open-source free QuickDup clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring candidates, or repeatable duplication. USE FOR: the repo wants QuickDup; the team needs repeatable duplicate-code scans for C#; the user asks about DRY…

managedcode/dotnet-skills · 138 tokens

MCPGateway: Skill for Codex