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/cst2989/react-tips-skill/no-unnecessary-effectsnpx skills add Cst2989/react-tips-skill --skill no-unnecessary-effectsgit clone --depth 1 https://github.com/Cst2989/react-tips-skillWrote 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/cst2989/react-tips-skill/no-unnecessary-effects)<a href="https://agentmods.dev/skills/cst2989/react-tips-skill/no-unnecessary-effects"><img src="https://agentmods.dev/badge/skills/cst2989/react-tips-skill/no-unnecessary-effects.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.1 | $0.00034 | $0.01291 |
| Opus 5 | $0.00017 | $0.00646 |
| Sonnet 5 | $0.00007 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
no-unnecessary-effects 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before Writing useEffect
Every time you are about to write a useEffect, stop and answer this question:
Is this syncing with an external system?
External systems: WebSocket, browser APIs (IntersectionObserver, navigator.onLine), third-party libraries (map SDKs, chart widgets), DOM measurements, setInterval timers.
NOT external systems: props, state, values derived from props or state, user events (clicks, form submissions).
If the answer is no, do NOT write the effect. Use the decision tree below to find the right alternative.
Decision Tree
Before writing the effect, check each case in order:
1. Am I transforming or deriving data?
Compute it inline. No state, no effect.
// NEVER do this
const [filtered, setFiltered] = useState([]);
useEffect(() => {
setFiltered(data.filter(item => item.active));
}, [data]);
// DO this
const filtered = data.filter(item => item.active);
// If genuinely expensive and not using React Compiler:
const filtered = useMemo(() => data.filter(item => item.active), [data]);
2. Am I responding to a user event?
Put the logic in the event handler. Effects respond to renders, not to user actions.
// NEVER do this
useEffect(() => {
if (submitted) {
performSearch(query);
setSubmitted(false);
}
}, [submitted, query]);
// DO this
function handleSubmit(e: FormEvent) {
e.preventDefault();
performSearch(query);
}
3. Am I resetting state when a prop changes?
Use the key prop to let React unmount and remount the component with fresh state.
// NEVER do this
useEffect(() => {
setComment('');
}, [userId]);
// DO this — in the parent
<UserProfile key={userId} userId={userId} />
4. Am I fetching data?
Use TanStack Query (React Query) or a similar library. If you must use useEffect, always add cleanup to ignore stale responses.
// Preferred
const { data, isLoading, error } = useQuery({
queryKey: ['user', userId],
queryFn: () => fetchUser(userId),
});
// If useEffect is unavoidable, always handle race conditions
useEffect(() => {
let ignore = false;
fetchUser(userId).then(data => {
if (!ignore) setUser(data);
});
return () => { ignore = true; };
}, [userId]);
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.
- 6d ago First seen · 188 lines · 34 tokens per session scan A 850d4847b0bc
no-unnecessary-effects is a skill published in the GitHub repository Cst2989/react-tips-skill (29 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,291 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-30.
Other skills, from other repositories
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…