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/petekp/claude-code-setup/react-change-reviewnpx skills add petekp/claude-code-setup --skill react-change-reviewgit clone --depth 1 https://github.com/petekp/claude-code-setupWrote 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/petekp/claude-code-setup/react-change-review)<a href="https://agentmods.dev/skills/petekp/claude-code-setup/react-change-review"><img src="https://agentmods.dev/badge/skills/petekp/claude-code-setup/react-change-review.svg" alt="Measured on agentmods" 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 | $0.00095 | $0.01605 |
| Opus 5 | $0.00048 | $0.00803 |
| Sonnet 5 | $0.00019 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00161 |
Grade A, and why
react-change-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 3d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Change Review
Review the most relevant recent React code changes, consolidate all signal from the React specialist skills, and return a stack-ranked hardening plan. Treat every valid finding as something that should be fixed; do not frame fixes as optional cleanup unless the evidence shows a real tradeoff.
Load Supporting Skills
Before reviewing, load and apply these skills:
$react-doctor: run or interpret diff-based React diagnostics.$vercel-react-best-practices: performance, data fetching, rendering, bundle, and server/client boundary review.$vercel-composition-patterns: component API and composition review.$react-useeffect: Effect, derived state, event logic, dependency, and cleanup review.
In this skill repository, the supporting skills normally exist as sibling folders:
../react-doctor/SKILL.md../vercel-react-best-practices/SKILL.md../vercel-composition-patterns/SKILL.md../react-useeffect/SKILL.md
If a support skill is missing, continue with the available guidance and state the gap in the final review.
Scope The Recent Changes
Determine the review scope intelligently from context. Prefer explicit user scope, then local git evidence.
Use this precedence:
- User-provided PR, branch, commit range, files, or feature area.
- Staged and unstaged changes in the working tree.
- Current branch diff against the best base branch.
- Recent commits on the current branch when the working tree is clean.
- Ask one concise question only if no reasonable scope can be inferred.
Useful commands:
git status --short
git diff --name-only --diff-filter=ACMR
git diff --cached --name-only --diff-filter=ACMR
git merge-base HEAD origin/main || git merge-base HEAD main || git merge-base HEAD origin/master || git merge-base HEAD master
git diff --name-only --diff-filter=ACMR "$base"...HEAD
git log --oneline --decorate -n 10
Include files that can affect React behavior:
.tsx,.jsx, React-facing.ts/.js- hooks, providers, stores, query/data modules, server actions, route loaders, API handlers used by React UI
- package, lint, build, or framework config changes that affect React runtime or bundling
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.
- 3d ago First seen · 151 lines · 95 tokens per session scan A 848c57bd8216
react-change-review is a skill published in the GitHub repository petekp/claude-code-setup (45 stars, last pushed 27d ago), licensed MIT. It adds 95 tokens to every session and 1,605 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
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
copilotkit-setup
Use when adding CopilotKit to an existing project or bootstrapping a new CopilotKit project from scratch. Covers framework detection, package installation, runtime wiring (managed Intelligence or self-hosted SSE), provider setup, and first working chat integration.
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
runtime
@copilotkit/runtime — mount a fetch-native CopilotRuntime on any JS server, wire middleware, pick an AgentRunner, instantiate BuiltInAgent (Factory Mode with TanStack AI is the preferred default) or plug in any of 12 external agent frameworks (Mastra, LangGraph, CrewAI Crews/Flows, PydanticAI, ADK, LlamaIndex, Agno…
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.