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 narpatsinghpurohit/tstack --skill reviewing-react-codegit clone --depth 1 https://github.com/narpatsinghpurohit/tstackWrote 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/narpatsinghpurohit/tstack/reviewing-react-code)<a href="https://agentmods.dev/skills/narpatsinghpurohit/tstack/reviewing-react-code"><img src="https://agentmods.dev/badge/skills/narpatsinghpurohit/tstack/reviewing-react-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/narpatsinghpurohit/tstack/reviewing-react-code"><img src="https://agentmods.dev/badge/skills/narpatsinghpurohit/tstack/reviewing-react-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.00085 | $0.00533 |
| Opus 5.5 | $0.00034 | $0.00213 |
| Sonnet 5.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 1mo 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.
- 1mo 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 6mo ago), licensed MIT. It adds 85 tokens to every session and 533 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
react-patterns
React 19 performance patterns and composition architecture for Vite + Cloudflare projects. 50+ rules ranked by impact — eliminating waterfalls, bundle optimisation, re-render prevention, composition over boolean props, server/client boundaries, and React 19 APIs. Use when writing, reviewing, or refactoring React…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.
review-system-design
Review a system design someone else provided - screenshot, drawio, Mermaid, slides, doc, or IaC - by extracting it into a confirmed fact sheet, then scoring it on the nine axes.
review-ticket
Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.
common-feedback-reporter
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.