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 wataru-maeda/react-native-boilerplate --skill review-codegit clone --depth 1 https://github.com/wataru-maeda/react-native-boilerplateWrote 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/wataru-maeda/react-native-boilerplate/review-code)<a href="https://agentmods.dev/skills/wataru-maeda/react-native-boilerplate/review-code"><img src="https://agentmods.dev/badge/skills/wataru-maeda/react-native-boilerplate/review-code/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/wataru-maeda/react-native-boilerplate/review-code"><img src="https://agentmods.dev/badge/skills/wataru-maeda/react-native-boilerplate/review-code.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.00033 | $0.00605 |
| Opus 5.5 | $0.00013 | $0.00242 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
review-code 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Code
Review the branch diff against repository rules. A review request does not authorize edits.
Inspect
- Choose the base from the branch table:
devfor work branches,mainfor hotfixes. Ask when the branch prefix does not identify one. - Read
git diff --name-only <base>...HEADandgit diff <base>...HEAD. - Read
AGENTS.md, including Git rules. - Exclude
package-lock.json,node_modules/,ios/,android/,dist/, andcoverage/from this rules review. Report excluded scope.
Review
- Check required utilities, file placement, names, imports, and types.
- Check
testIDs and Maestro flows for new screens, and tests beside new components. - Check branch names and commit messages against Git rules.
- Report only issues introduced by the diff. Do not flag unrelated existing code.
- Cite a rule for each violation. Label uncertainty as advisory. Label any personal suggestion as outside the rules.
Required Reviews
- Read and run the security review.
- Read and run the license review.
- Use the same base and head as this review for both. Exclude unrelated uncommitted work.
- Include both review results in the report. Record findings, limitations, and any dependencies or assets that could not be checked. If license review finds no relevant changes, state that explicitly.
- Recheck affected findings if the diff changes after review. Do not reuse results from an older diff.
Complete both reviews before reporting. Do not treat a missing or incomplete review as a pass.
Report
Lead with the important findings. For each finding, give the file and line, rule heading, observed behavior, required behavior, and suggested fix.
- Separate violations from advisories.
- State the number of files reviewed and findings.
- Say explicitly when no violations were found.
- Include at most two useful examples of compliance.
- Do not claim unrun checks passed.
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.
- yesterday First seen · 59 lines · 33 tokens per session scan A 5b1145f43568
review-code is a skill published in the GitHub repository wataru-maeda/react-native-boilerplate (520 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 605 once invoked, about $0.0001 per session on Opus 5.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-10-19.
Other skills, from other repositories
react-native
Use when writing the JS/TS inside a React Native or Expo app — screens, Expo Router navigation, lists, Reanimated gestures, platform forks, offline state, native modules — or killing jank and render storms. NOT eas build/submit/OTA/config-plugin (that is expo), NOT a Dart app (that is flutter), NOT web React/DOM (that…
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
expo
Use when shipping a React Native app with Expo — EAS Build/Submit/Update, eas.json profiles and channels, config plugins, prebuild/CNG, runtime-version policy, OTA updates that never land, SDK upgrades, the New Architecture. NOT RN UI, navigation or native-module authoring (that is react-native), NOT a Dart app (that…
pr-evidence
Use when opening or updating a pull request whose diff touches apps/leclap-web or apps/leclap-expo. Its description must carry before/after snapshots and a before/after evidence video rendered with LeClap itself. Covers what to capture, how to render the video, where the media live and how to embed them.
migrate-nativewind-to-uniwind
Migrate a React Native project from NativeWind to Uniwind. Use when the user wants to replace NativeWind with Uniwind, upgrade from NativeWind, switch to Uniwind, or mentions NativeWind-to-Uniwind migration. Handles package removal, config migration, Tailwind 4 upgrade, cssInterop removal, theme conversion, and all…
spec-harness-generate-agents
Bind the 6 SDD agents to THIS project's rules — fill each agent's GEN:rules region with its concern's real rules (implementer←Coding, tester←Testing+commands, reviewer←Reviewing, researcher/planner←Architecture, verifier←goal). Use when Malik says 'generate the agents', 'make the agents project-specific', 'bind agents…