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 commands/farzannajipour/cursor-react-rules/refactor-componentgit clone --depth 1 https://github.com/Farzannajipour/cursor-react-rulesWhat 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.00000 | $0.00541 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
refactor-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 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Component
Overview
Refactor an existing component to improve code quality, performance, and maintainability.
Steps
-
Analyze current component
- Identify code smells
- Check component size (>200 lines?)
- Look for duplicated logic
- Review performance
-
Extract logic
- Move business logic to custom hooks
- Extract sub-components
- Create utility functions
-
Improve types
- Add missing TypeScript types
- Remove 'any' types
- Add JSDoc comments
-
Optimize performance
- Add React.memo if needed
- Use useMemo for expensive calculations
- Use useCallback for function props
-
Improve accessibility
- Add ARIA labels
- Ensure keyboard navigation
- Add semantic HTML
Refactoring Checklist
- Component under 200 lines
- No code duplication
- Business logic in custom hooks
- All TypeScript types defined
- No 'any' types
- Performance optimized
- Accessibility improved
- Tests updated
- Functionality unchanged
Common Refactoring Patterns
Extract Custom Hook
// Before
function Component() {
const [data, setData] = useState([]);
const [loading, setLoading] = useState(false);
useEffect(() => {
// fetch logic
}, []);
return <div>{/* JSX */}</div>;
}
// After
function useData() {
const [data, setData] = useState([]);
const [loading, setLoading] = useState(false);
useEffect(() => {
// fetch logic
}, []);
return { data, loading };
}
function Component() {
const { data, loading } = useData();
return <div>{/* JSX */}</div>;
}
Extract Sub-component
// Before
function LargeComponent() {
return (
<div>
<div className="header">{/* header JSX */}</div>
<div className="content">{/* content JSX */}</div>
<div className="footer">{/* footer JSX */}</div>
</div>
);
}
// After
function Header() { /* ... */ }
function Content() { /* ... */ }
function Footer() { /* ... */ }
function LargeComponent() {
return (
<div>
<Header />
<Content />
<Footer />
</div>
);
}
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 · 106 lines · 0 tokens per session scan A fbf99256ceb8
refactor-component is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 541 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.