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 commands/jezweb/claude-skills/react-patternsgit clone --depth 1 https://github.com/jezweb/claude-skillsWrote 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/commands/jezweb/claude-skills/react-patterns)<a href="https://agentmods.dev/commands/jezweb/claude-skills/react-patterns"><img src="https://agentmods.dev/badge/commands/jezweb/claude-skills/react-patterns.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.00016 | $0.00073 |
| Opus 5 | $0.00008 | $0.00036 |
| Sonnet 5 | $0.00003 | $0.00015 |
| Haiku 4.5 | $0.00002 | $0.00007 |
Grade A, and why
react-patterns 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 today.
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
Load the react-patterns skill.
If $ARGUMENTS contains a file path, review it against the patterns in priority order. Otherwise review the current project's React code starting from the most critical categories.
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.
- today First seen · 9 lines · 16 tokens per session scan A 03526eaa40e3
react-patterns is a command published in the GitHub repository jezweb/claude-skills (993 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 73 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-09-03.
Other commands, from other repositories
frontend
Injects context of all relevant cli files.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
doc
Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.
speckit-gaia-plan-close
Close a plan after implementation+merge. Offers wiki-promote for the plan's consolidated SUMMARY.md, cold-consolidates an out-of-band merge, then early-reaps the local plan folder once cost is represented in cost.jsonl.
speckit-gaia-spec-close
Close a SPEC after implementation+merge. Optional drain of deferred wiki-promote, cold-consolidates an out-of-band merge into SUMMARY.md, then early-reaps the local SPEC folder once cost is represented in cost.jsonl.
speckit.clarify
This project uses the GAIA preset. Bare /speckit-clarify is not the clarify path here: core clarify writes an off-shape artifact (a ## Clarifications / ### Session block with five-word answers) and carries a question cap GAIA does not use. Run /gaia-spec instead — it drives GAIA's coverage-based Socratic clarify loop…