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/narpatsinghpurohit/tstack/reviewing-react-codenpx skills add narpatsinghpurohit/tstack --skill reviewing-react-codegit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWhat 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.00085 | $0.00533 |
| Opus 5 | $0.00043 | $0.00267 |
| Sonnet 5 | $0.00017 | $0.00107 |
| Haiku 4.5 | $0.00009 | $0.00053 |
Grade A, and why
reviewing-react-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 2d 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.
What it actually says
Reviewing React Code
Severity levels
- NON-NEGOTIABLE: Blocks merge. No exceptions.
- CRITICAL: Must fix before merge.
- SUGGESTION: Should fix. Improves quality.
- NICE-TO-HAVE: Optional polish.
Review process
- Read the code under review
- Check against every non-negotiable rule in
rules/ - Check permission coverage using the
permission-guidelinesskill - Check against critical and suggestion items below
- Output findings in the format at the bottom
Non-negotiable rules (always read these)
- rules/feature-structure.md — 3-file split, view purity, glue simplicity
- rules/import-boundaries.md — No cross-feature imports, import direction
- rules/security.md — XSS, injection, secrets
- rules/hooks.md — useEffect, cleanup, dependencies
- rules/accessibility.md — WCAG 2.2 AA keyboard, focus, labels
- rules/component-design.md — Single responsibility, state ownership
- rules/type-safety.md — No any, no ts-ignore
Output format
## Code Review: [Component/Feature Name]
### NON-NEGOTIABLE (blocks merge)
- **[File:Line]** [Rule ID]: [Description and exact fix]
### Critical
- **[File:Line]**: [Description and fix]
### Suggestions
- **[File:Line]**: [Recommendation]
### Passed
- [Categories that passed all checks]
References
What ships with it
9 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.
- 2d ago First seen · 58 lines · 85 tokens per session scan A 12bc79dffdbc
reviewing-react-code is a skill published in the GitHub repository narpatsinghpurohit/tstack (5 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 533 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
row-selection
Maintain rowSelection ID state with stable getRowId, single, multi, subrow, and Shift-range rules, selected row models, handler anchors, and manual-pagination semantics. Load when implementing getToggleSelectedHandler, enableRowRangeSelection, selectChildren, deselectParents, or selected IDs that outlive loaded Row…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
wrdn-effect-atom-optimistic
Detects hand-rolled optimistic-update plumbing in React code that should be using effect-atom's Atom.optimistic and Atom.optimisticFn instead. Run on diffs touching packages/react/src/api/atoms.tsx, packages/react/src/pages//.tsx, or any file that imports an effect-atom mutation atom from ./api/atoms. The hand-rolled…