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/justanesta/claude-code-resources/webdev-react-patternsnpx skills add justanesta/claude-code-resources --skill webdev-react-patternsgit clone --depth 1 https://github.com/justanesta/claude-code-resourcesWhat 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.00031 | $0.01861 |
| Opus 5 | $0.00015 | $0.00931 |
| Sonnet 5 | $0.00006 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
webdev-react-patterns scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(url, { signal: controller.signal }) How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Patterns & Best Practices
Core Principles
- Composition over inheritance — Build complex UIs by combining small, focused components
- Hooks for all logic — Use hooks to encapsulate stateful logic and side effects. Never use class components
- Unidirectional data flow — Data flows down via props; events flow up via callbacks
- Colocation — Place state, styles, tests, and types next to the components that use them
- Type safety everywhere — Use TypeScript for props, state, context, and hook return types
Hooks Fundamentals
function Search({ items, onSelect }: { items: string[]; onSelect: (item: string) => void }) {
const [query, setQuery] = useState("");
const inputRef = useRef<HTMLInputElement>(null);
const filtered = useMemo(
() => items.filter((item) => item.toLowerCase().includes(query.toLowerCase())),
[items, query]
);
const handleSelect = useCallback(
(item: string) => { setQuery(""); onSelect(item); },
[onSelect]
);
useEffect(() => { inputRef.current?.focus(); }, []);
return (
<div>
<input ref={inputRef} value={query} onChange={(e) => setQuery(e.target.value)} />
{filtered.map((item) => (
<button key={item} onClick={() => handleSelect(item)}>{item}</button>
))}
</div>
);
}
See hooks-patterns for:
- Rules of hooks, useId, useRef patterns
- Cleanup functions and dependency array pitfalls
Custom Hooks
function useFetch<T>(url: string) {
const [data, setData] = useState<T | null>(null);
const [error, setError] = useState<Error | null>(null);
const [loading, setLoading] = useState(true);
useEffect(() => {
const controller = new AbortController();
setLoading(true);
fetch(url, { signal: controller.signal })
.then((res) => { if (!res.ok) throw new Error(`HTTP ${res.status}`); return res.json(); })
.then((json) => setData(json as T))
.catch((err) => { if (err.name !== "AbortError") setError(err); })
.finally(() => setLoading(false));
return () => controller.abort();
}, [url]);
return { data, error, loading };
}
What ships with it
6 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 · 211 lines · 31 tokens per session scan A 7a7426e50efa
webdev-react-patterns is a skill published in the GitHub repository justanesta/claude-code-resources (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 1,861 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…