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/korbinjoe/teemai/code-reviewer-reactnpx skills add korbinjoe/TeemAI --skill code-reviewer-reactgit clone --depth 1 https://github.com/korbinjoe/TeemAIWhat 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.00077 | $0.01846 |
| Opus 5 | $0.00039 | $0.00923 |
| Sonnet 5 | $0.00015 | $0.00369 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade A, and why
code-reviewer-react 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning
Focused on logic and structure review of React + TypeScript frontend code. Checks whether code is correct, robust, and maintainable.
Difference from code-audit: code-audit focuses on CSS/styling/visual aspects (spacing, colors, responsiveness);
this skill focuses on JS/TS logic (component design, types, Hooks, performance, error handling).
Execution timing: After code submission, before merge; or when user explicitly requests review
Scan scope: Specified files, or file list obtained via git diff
Review Process
Step 1: Determine Review Scope
Determine files to review by priority:
- Files or directories explicitly specified by user
- User mentions PR or branch → run
git diff --name-only <base>..HEADto get changed files - User says "look at recent changes" → run
git diff --name-only HEAD~1to get last commit changes - None of the above → ask user which files to review
Only review .ts / .tsx / .js / .jsx files. Skip test files (*.test.* / *.spec.*),
type declaration files (*.d.ts), and config files.
Step 2: Per-file Review
Read the complete file content first, understand context, then check each item. Don't just look at the diff — local changes may introduce problems in the global context. Execute the following review items for each file.
Step 3: Summary Report
Generate a structured report using the output template at the bottom.
Review Checklist
1. Component Design
Good components are highly cohesive and loosely coupled. Check whether components have single responsibility and clear interfaces.
Check items:
- Single component exceeds 300 lines → suggest splitting into sub-components
- More than 8 Props → may need consolidation into an object or component splitting
- Components defined inside other components (nested definitions) → recreated every render, causing state loss
- Prop drilling (props passed through 2+ layers) → consider Context or composition patterns
- Component handles both data fetching and UI rendering → suggest separating into container + presentational
- Unused props or imports
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 · 195 lines · 77 tokens per session scan A 840cd2807580
code-reviewer-react is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 1,846 once invoked, about $0.0004 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
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
react-core
@copilotkit/react-core — mount the CopilotKit provider (from @copilotkit/react-core/v2) in a Next.js App Router / React Router v7 / TanStack Start / SPA app, drop in CopilotChat/CopilotPopup/CopilotSidebar (v2 chat components ship from react-core/v2 — NOT react-ui, which is CSS-only in v2), access and subscribe to…
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API ( component, addTransitionType, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components…
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.