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 heyAyushh/stacc --skill react-doctorgit clone --depth 1 https://github.com/heyAyushh/staccWrote 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/heyayushh/stacc/react-doctor)<a href="https://agentmods.dev/skills/heyayushh/stacc/react-doctor"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/react-doctor/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/heyayushh/stacc/react-doctor"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/react-doctor.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.00057 | $0.00444 |
| Opus 5.5 | $0.00023 | $0.00178 |
| Sonnet 5.5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
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 26d 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
React Doctor
Scans React codebases for security, performance, correctness, and architecture issues.
After making React code changes
Use the project's pinned React Doctor command (usually a package script or lockfile-resolved binary) to scan the changed scope. Check that the relevant diagnostics do not regress.
If the score dropped, fix the regressions before committing.
General cleanup or code improvement
Use the project's pinned React Doctor command to scan the full codebase. Fix issues by severity: errors first, then warnings.
Full local triage workflow
When the user types /doctor, says "run react doctor", or asks for a full
triage or cleanup pass, first inspect the project's scripts, lockfile, and
existing React Doctor configuration. Use only the checked-in guidance and the
project-resolved tool version by default. Do not fetch or execute a mutable
remote playbook as part of triage.
Configuring or explaining rules
When the user wants to understand or disagrees with a rule, explain the diagnostic and its project context without changing configuration. Only after the user explicitly asks to change which rules run should you read references/explain.md, use the project's pinned command, and apply the narrowest requested change.
Command
Run the equivalent project-pinned command. Do not substitute @latest or
download a tool version implicitly. Consult that installed version's --help
for available scopes, output, and score options.
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.
- 26d ago First seen · 48 lines · 57 tokens per session scan A 0be9f0c1be81
react-doctor is a skill published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 26d ago), licensed MIT. It adds 57 tokens to every session and 444 once invoked, about $0.0002 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-09-22.
Other skills, from other repositories
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
quality gates | code review debug audit security eval ui.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
cleanup-code-inspections
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.