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/tugkanboz/awesome-cursorrules/component-developmentgit clone --depth 1 https://github.com/tugkanboz/awesome-cursorrulesWhat 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.03226 |
| Opus 5 | $0.00000 | $0.01613 |
| Sonnet 5 | $0.00000 | $0.00645 |
| Haiku 4.5 | $0.00000 | $0.00323 |
Grade A, and why
component-development 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 — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React TypeScript Component Excellence
Modern Component Architecture
- Functional Components: Use React hooks for state and lifecycle management
- TypeScript Integration: Comprehensive type safety with proper interface definitions
- Performance Optimization: Implement useMemo, useCallback, and React.memo strategically
- Accessibility First: Built-in ARIA support and keyboard navigation
Component Structure Best Practices
import React, { useState, useCallback, useMemo, ReactNode } from 'react'
import { clsx } from 'clsx'
// ✅ Define comprehensive prop interfaces
interface ButtonProps {
children: ReactNode
variant?: 'primary' | 'secondary' | 'outline' | 'ghost'
size?: 'sm' | 'md' | 'lg'
disabled?: boolean
loading?: boolean
onClick?: (event: React.MouseEvent<HTMLButtonElement>) => void
type?: 'button' | 'submit' | 'reset'
className?: string
'data-testid'?: string
}
// ✅ Modern functional component with comprehensive TypeScript
export const Button: React.FC<ButtonProps> = ({
children,
variant = 'primary',
size = 'md',
disabled = false,
loading = false,
onClick,
type = 'button',
className,
'data-testid': testId,
...rest
}) => {
// ✅ Memoized class computation for performance
const buttonClasses = useMemo(() => clsx(
'btn',
`btn--${variant}`,
`btn--${size}`,
{
'btn--disabled': disabled,
'btn--loading': loading,
},
className
), [variant, size, disabled, loading, className])
// ✅ Optimized event handler
const handleClick = useCallback((event: React.MouseEvent<HTMLButtonElement>) => {
if (disabled || loading) {
event.preventDefault()
return
}
onClick?.(event)
}, [disabled, loading, onClick])
return (
<button
type={type}
className={buttonClasses}
onClick={handleClick}
disabled={disabled || loading}
aria-disabled={disabled || loading}
aria-busy={loading}
data-testid={testId}
{...rest}
>
{loading && (
<span className="btn__spinner" aria-hidden="true">
<LoadingSpinner size="sm" />
</span>
)}
<span className={loading ? 'btn__content--loading' : 'btn__content'}>
{children}
</span>
</button>
)
}
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 · 523 lines · 3,226 tokens per session scan A 24b6ee1f5b7f
component-development is a cursor rule published in the GitHub repository tugkanboz/awesome-cursorrules (20 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,226 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-30.
Other cursor rules, from other repositories
cursorrules
You are building an AI/ML project with Python. The project uses PyTorch for model training, handles data pipelines with proper validation, tracks experiments systematically, and follows production ML engineering practices. Code is type-hinted, tested, and reproducible.
unity-input
Guidelines for working with the New Input System in Unity 6.2.
unity-ui
Assets/ ├── UI/ │ ├── Runtime/ │ │ ├── Controllers/ │ │ │ └── MainMenuController.cs │ │ ├── Views/ │ │ │ └── MainMenuView.cs │ │ ├── ViewModels/ │ │ │ └── HealthViewModel.cs │ │ ├── UXML/ │ │ │ └── MainMenu.uxml │ │ └── USS/ │ │ └── MainMenu.uss │ └── Editor/ │ └── UIBuilderExtensions.cs.
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.