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 rules/mn-lizard-team/aiyu-multi-agent/react-developergit clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/rules/mn-lizard-team/aiyu-multi-agent/react-developer)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/react-developer"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/react-developer.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.00070 | $0.01750 |
| Opus 5 | $0.00035 | $0.00875 |
| Sonnet 5 | $0.00014 | $0.00350 |
| Haiku 4.5 | $0.00007 | $0.00175 |
Grade A, and why
react-developer 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 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.
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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: react-developer
Cursor Agent-Requested Rule — invoke via
@react-developeror let the AI auto-select.
Skills: clean-code, frontend-design, nextjs-react-expert Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
react-developer| Skills:clean-code, frontend-design, nextjs-react-expert| Rules:GEMINI, api-design-rules, deployment-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- React components
- hooks
- context
- state management
- React patterns
React Developer
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"React is a library, not a framework. You choose your own adventure—which means you need to know which choices to make."
Modern React (18+)
Hooks-First Approach
// ✅ Good: Hooks for logic
function useUser(userId: string) {
const [user, setUser] = useState<User | null>(null);
const [loading, setLoading] = useState(true);
useEffect(() => {
let cancelled = false;
fetchUser(userId).then(data => {
if (!cancelled) {
setUser(data);
setLoading(false);
}
});
return () => { cancelled = true; };
}, [userId]);
return { user, loading };
}
// Usage
function UserProfile({ userId }: { userId: string }) {
const { user, loading } = useUser(userId);
if (loading) return <Skeleton />;
if (!user) return <NotFound />;
return <UserCard user={user} />;
}
Custom Hooks Pattern
// Encapsulate related logic
function useForm<T>(initialValues: T) {
const [values, setValues] = useState<T>(initialValues);
const [errors, setErrors] = useState<Partial<Record<keyof T, string>>>({});
const handleChange = (field: keyof T) => (value: any) => {
setValues(prev => ({ ...prev, [field]: value }));
};
const validate = (validators: Record<keyof T, (val: any) => string | undefined>) => {
const newErrors: typeof errors = {};
let valid = true;
for (const [field, validator] of Object.entries(validators)) {
const error = validator(values[field]);
if (error) {
newErrors[field as keyof T] = error;
valid = false;
}
}
setErrors(newErrors);
return valid;
};
return { values, errors, handleChange, validate, setValues };
}
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 · 266 lines · 70 tokens per session scan A aad6b1f2338a
react-developer is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,750 once invoked, about $0.0003 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 cursor rules, from other repositories
react
React and TypeScript conventions for the frontend.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.