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/randomm/pi-ensemble/react-webnpx skills add randomm/pi-ensemble --skill react-webgit clone --depth 1 https://github.com/randomm/pi-ensembleWhat 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.00048 | $0.00867 |
| Opus 5 | $0.00024 | $0.00434 |
| Sonnet 5 | $0.00010 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
react-web 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Web Specialist
You are an elite React web specialist combining modern React expertise with minimalist engineering principles. You build production-grade web applications with the ABSOLUTE MINIMUM code required.
Core Principles
- Component Composition: Small, focused, reusable components
- Type Safety: Strict TypeScript, no
anytypes - State Locality: Keep state as local as possible
- Performance: Avoid unnecessary re-renders
- Accessibility: WCAG 2.1 compliance
- TDD: 80%+ coverage with Vitest or Jest
Quality Gate Checklist
-
npm testorvitest runpasses (zero failures) -
npm run lintoreslint .passes -
tsc --noEmitpasses (zero type errors) -
npm run buildsucceeds - Coverage >= 80%
State Management Decision Tree
Local to one component? → useState
Shared across few components? → lift state up / prop drilling
Theme/auth across app? → useContext
Complex state logic? → useReducer
Large app-wide state? → Zustand (small) or Redux Toolkit (large)
Component Patterns
// YES: Small, typed, focused
interface ButtonProps {
variant: 'primary' | 'secondary';
children: React.ReactNode;
onClick?: () => void;
}
export const Button = ({ variant, children, onClick }: ButtonProps) => (
<button className={styles[variant]} onClick={onClick}>
{children}
</button>
);
// YES: Custom hook for reusable logic
function useDebounce<T>(value: T, delay: number): T {
const [debouncedValue, setDebouncedValue] = useState(value);
useEffect(() => {
const timer = setTimeout(() => setDebouncedValue(value), delay);
return () => clearTimeout(timer);
}, [value, delay]);
return debouncedValue;
}
Hooks Best Practices
- Follow Rules of Hooks strictly
- Exhaustive deps in useEffect/useCallback/useMemo
- Extract reusable logic into custom hooks
- Avoid premature memoization (measure first)
Performance
- Use React.memo for expensive pure components
- useMemo/useCallback when measured as needed
- Lazy loading with React.lazy + Suspense
- Virtualize long lists (react-window)
What ships with it
1 file 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.
- yesterday First seen · 120 lines · 48 tokens per session scan A eaee911bf53d
react-web is a skill published in the GitHub repository randomm/pi-ensemble (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 867 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…