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.
git 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/commands/mn-lizard-team/aiyu-multi-agent/react)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/react"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/react/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/react"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/react.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00427 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
react 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.
What it actually says
/react
React development — modern UI with hooks, context, and state management. Used for interactive UIs with a rich ecosystem and flexibility.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `react-developer`** | Skills: `clean-code, frontend-design, nextjs-react-expert`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Read the agent's full instructions from
.windsurf/agents/react-developer.md(or.cursor/rules/agents/react-developer.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- Follow clean-code principles: concise, no over-engineering, self-documenting
/react — React Development
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `react-developer`** | Skills: `clean-code, frontend-design, nextjs-react-expert`
Task
Build modern React applications with hooks-first patterns and proper state management.
Steps:
-
Component Design
- Functional components
- Hooks for logic (useState, useEffect, custom)
- Props vs State decisions
-
State Management
- useState/useReducer for local
- Context for shared
- Zustand/Redux for app-wide
-
Performance
- useMemo/useCallback
- React.memo
- Code splitting with lazy/Suspense
-
Patterns
- Compound components
- Custom hooks
- Render props
- HOCs (when needed)
Usage Examples
/react build component library
/react implement custom hooks
/react setup Zustand state management
/react optimize with memoization
/react create compound component
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 · 78 lines · 0 tokens per session scan A 3ee02f7a0bee
react is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 427 tokens. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.