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 skills/managedcode/dotpilot/mcaf-human-review-planningnpx skills add managedcode/dotPilot --skill mcaf-human-review-planninggit clone --depth 1 https://github.com/managedcode/dotPilotWhat 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.00076 | $0.01195 |
| Opus 5 | $0.00038 | $0.00598 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
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 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.
This is a copy
97% identical to dotnet-mcaf-human-review-planning — 4 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.
How it starts
The opening of the file, as written. The whole thing — 124 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.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith 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.
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.
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 · 124 lines · 76 tokens per session scan A 0bd6efbe19d2
mcaf-human-review-planning is a skill published in the GitHub repository managedcode/dotPilot (23 stars, last pushed 4mo ago), licensed MIT. It adds 76 tokens to every session and 1,195 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to dotnet-mcaf-human-review-planning, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.
software-cost-estimator
Estimate developer cost and effort for a set of use cases, functional and non-functional requirements on a given technology stack. Produces an architecture plan, a role-resolved man-hour estimate with P50/P85/P95 ranges, a side-by-side comparison of four delivery modes (human only, human + AI, AI-steered…
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
skill-to-subagent
Turn an existing pi skill into an isolated subagent and wire it into a project's implementation pipeline. Decides fitness first, writes the bridge agent, routes the model, tunes context inheritance, and wires a spawn checkpoint. Use on "wrap this skill as a subagent", "turn X into a subagent", "should this be a…