review

review is a skill for Claude Code from team-attention/plugins-for-claude-natives. It costs 41 tokens per session (631 once invoked), scanned A, original, MIT.

A skill for opening an interactive web review of content such as a plan, document, or code-related text. Reviewers can approve or reject items with checkboxes and leave comments.

In plain words
What is it for?
Use it when reviewing a file, supplied text, or recently discussed content, then process the submitted feedback.
Why use it?
It gives people a clear place to provide structured feedback instead of relying on an informal conversation or scattered edits.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the interactive-review plugin — 1 skill, 1 MCP server shipped together

Good fit Use it when reviewing a file, supplied text, or recently discussed content, then process the submitted feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/team-attention/plugins-for-claude-natives/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 team-attention/plugins-for-claude-natives --skill review
Clone the repo
git clone --depth 1 https://github.com/team-attention/plugins-for-claude-natives

Made for: Claude Code.

Or install interactive-review, the plugin that ships this one along with the rest of its 1 skill, 1 MCP server.

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 review

README.md
[![agentmods](https://agentmods.dev/badge/skills/team-attention/plugins-for-claude-natives/review/github.svg)](https://agentmods.dev/skills/team-attention/plugins-for-claude-natives/review)
Your own site
<a href="https://agentmods.dev/skills/team-attention/plugins-for-claude-natives/review"><img src="https://agentmods.dev/badge/skills/team-attention/plugins-for-claude-natives/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 review

Your own site · 80×15
<a href="https://agentmods.dev/skills/team-attention/plugins-for-claude-natives/review"><img src="https://agentmods.dev/badge/skills/team-attention/plugins-for-claude-natives/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 631 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 pass 7 Sept 2026
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.00041 $0.00631
Opus 5 $0.00020 $0.00316
Sonnet 5 $0.00008 $0.00126
Haiku 4.5 $0.00004 $0.00063

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

Security

Grade A, and why

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 10d 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/interactive-review/skills/review/SKILL.md · 90 lines

How it starts

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

Interactive Review Skill

This skill opens an interactive web UI where users can review content with checkboxes and comments.

How It Works

  1. Determine the content source:
    • If user specifies a file path: Use the Read tool to get the file contents
    • If user provides content directly: Use that content as-is
    • Otherwise: Collect the most recent relevant content from the conversation
  2. Call mcp__interactive_review__start_review with the content
  3. A browser window opens automatically with the review UI
  4. User reviews each item:
    • Check/uncheck to approve/reject
    • Add optional comments
  5. User clicks Submit
  6. Process the feedback and respond accordingly

Content Sources (Priority Order)

  1. Explicit file path: User says "review /path/to/file.md" or "이 파일 리뷰해줘: README.md"
    • Read the file using Read tool and use its contents
  2. Direct content: User provides or references specific content to review
    • Use the provided content directly
  3. Conversation context: Extract relevant content from recent conversation
    • Plans, documents, code, etc. that were recently discussed

Usage

When the user wants to review content:

# If file path is specified, read it first:
Read({ "file_path": "/path/to/file.md" })

# Then start the review:
mcp__interactive_review__start_review({
  "content": "<content from file or conversation>",
  "title": "<descriptive title>"
})

Processing Results

The tool returns a JSON with review items. Handle each item based on:

checked comment Action
true empty Approved - proceed as planned
true has text Approved with note - consider the feedback
false has text Rejected - modify according to comment
false empty Rejected - remove or reconsider this item

Example Flow

User: "Review this implementation plan"

  1. Extract the plan content from recent output
  2. Call start_review with the content
  3. Wait for user feedback (tool blocks until submit)
  4. Present summary of feedback
  5. Ask if user wants you to proceed with approved items or revise rejected items

Read the full file on GitHub · 90 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. 10d ago First seen · 90 lines · 41 tokens per session scan A 6700f5593988

Subscribe to this mod's changes

review is a skill published in the GitHub repository team-attention/plugins-for-claude-natives (824 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 631 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens