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 85danf/agent-skills --skill review-plan-team-modegit clone --depth 1 https://github.com/85danf/agent-skillsWrote 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/85danf/agent-skills/review-plan-team-mode)<a href="https://agentmods.dev/skills/85danf/agent-skills/review-plan-team-mode"><img src="https://agentmods.dev/badge/skills/85danf/agent-skills/review-plan-team-mode/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/skills/85danf/agent-skills/review-plan-team-mode"><img src="https://agentmods.dev/badge/skills/85danf/agent-skills/review-plan-team-mode.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.00095 | $0.01407 |
| Opus 5 | $0.00048 | $0.00704 |
| Sonnet 5 | $0.00019 | $0.00281 |
| Haiku 4.5 | $0.00010 | $0.00141 |
Grade A, and why
review-plan-team-mode 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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing Plan Against Design
Verify that implementation plans are correctly derived from their source design documents using a team of parallel reviewer agents.
Prerequisite: Requires experimental agent teams. Enable CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS in settings.json or environment.
Workflow
Step 1: Classify Input Files
Examine every @-referenced file. Classify each as design or plan:
| Signal | Design doc | Plan doc |
|---|---|---|
| Filename contains | architecture, design, brainstorm, spec, rfc, requirements |
plan, implementation, task, phase, batch |
| Content structure | Goals, principles, decisions, tradeoffs, diagrams | Steps, tasks, acceptance criteria, pseudocode, file paths |
| Tone | "We should...", "The system will...", "Key decision:" | "Create file X", "Add method Y", "Step 1: implement..." |
If classification is ambiguous for any file, ask the user. Do not guess.
Step 2: Determine Mapping Strategy
| Scenario | Strategy |
|---|---|
| 1 design + 1 plan | Direct. One review pair. |
| 1 design + N plans | Auto-map all plans to the single design. N pairs. |
| N designs + M plans | Ask the user to map them explicitly. |
For N:M, prompt the user:
I found multiple design and plan docs. Which design verifies which plan(s)?
Design docs: design-auth.md, design-api.md
Plan docs: plan-auth.md, plan-api.md, plan-integration.md
Example: "design-auth -> plan-auth, design-api -> plan-api + plan-integration"
Step 3: Create Team and Spawn Reviewers
What ships with it
1 file 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.
- 9d ago First seen · 163 lines · 95 tokens per session scan A 706e0ee8af90
review-plan-team-mode is a skill published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 1,407 once invoked, about $0.0005 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.