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/new1direction/korgex/react-doctornpx skills add New1Direction/korgex --skill react-doctorgit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/react-doctor)<a href="https://agentmods.dev/skills/new1direction/korgex/react-doctor"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/react-doctor.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.00023 | $0.00375 |
| Opus 5 | $0.00012 | $0.00187 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
react-doctor 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 4d 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
When you've written or changed React/JSX (components, hooks, state, effects), run react-doctor — a deterministic linter that catches the mistakes agents commonly make in React — before calling the work done.
- Run it (no install needed — it's an
npxCLI; requires Node):npx react-doctor@latestOn a large repo, scope to the files you touched. - Read the report. It flags issues across: state & effects (stale closures, missing/incorrect effect deps, unnecessary effects), performance (avoidable re-renders, missing memoization, unstable props/children), architecture, security, and accessibility.
- Fix what it flags, judging each in context. react-doctor is deterministic (rule-based), so treat findings as real — but verify each fix preserves intent. Address the cause; don't blindly silence a rule.
- Re-run to confirm the issues you touched are gone and you didn't add new ones.
- If the project has a
doctor.config.{ts,js,json}, respect it — it tunes which rules run.
This is the "your agent writes bad React → this catches it" check: cheap, fast, and
it catches the bug classes that slip past a quick read. (react-doctor also ships an
install command that drops editor skills/rules, and an experimental LSP server —
but for an agent loop, running the CLI on your diff is the direct path.)
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.
- 4d ago First seen · 30 lines · 23 tokens per session scan A a469eea4efb3
react-doctor is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 375 once invoked, about $0.0001 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
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.
nextjs-fullstack
Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.
cr-next-type-llm
Cursor rules for next-type-llm.
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".