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/Farzannajipour/cursor-react-rulesWrote 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/farzannajipour/cursor-react-rules/create-component)<a href="https://agentmods.dev/commands/farzannajipour/cursor-react-rules/create-component"><img src="https://agentmods.dev/badge/commands/farzannajipour/cursor-react-rules/create-component/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/farzannajipour/cursor-react-rules/create-component"><img src="https://agentmods.dev/badge/commands/farzannajipour/cursor-react-rules/create-component.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.00334 |
| Opus 5.5 | $0.00000 | $0.00134 |
| Sonnet 5.5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
create-component 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 1mo 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
Create Component
Overview
Create a new React component following project standards with TypeScript, Tailwind CSS, and proper accessibility.
Steps
-
Determine component type
- UI component (buttons, inputs, cards)
- Feature component (user profiles, product cards)
- Layout component (headers, sidebars)
-
Generate component structure
- Create TypeScript interface for props
- Use functional component with proper typing
- Add Tailwind CSS classes
- Include accessibility attributes (ARIA labels, roles)
-
Add component features
- Loading state (if async)
- Error state (if can fail)
- Empty state (if displays data)
- Variants (if multiple styles needed)
-
Export properly
- Use named export
- Place in appropriate directory (components/ui or components/features)
Template
interface [ComponentName]Props {
// Define props based on requirements
className?: string;
children?: React.ReactNode;
}
export function [ComponentName]({ className, children, ...props }: [ComponentName]Props) {
return (
<div className={cn('[base-classes]', className)} {...props}>
{children}
</div>
);
}
Checklist
- TypeScript interface defined
- Proper naming (PascalCase)
- Tailwind CSS styling
- Accessibility attributes added
- Loading/error states (if needed)
- Named export used
- File placed in correct directory
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.
- 1mo ago First seen · 53 lines · 0 tokens per session scan A 8305e2009d92
create-component is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 334 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-08-31.
Other commands, from other repositories
react
Apply React with TypeScript best practices.
discover-frontend
Load frontend skills (React, Next.js, TypeScript, state management).
create-component
Create a new React component with TypeScript.
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.