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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/react-components)<a href="https://agentmods.dev/rules/technickai/ai-coding-config/react-components"><img src="https://agentmods.dev/badge/rules/technickai/ai-coding-config/react-components/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/rules/technickai/ai-coding-config/react-components"><img src="https://agentmods.dev/badge/rules/technickai/ai-coding-config/react-components.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.00521 |
| Opus 5.5 | $0.00000 | $0.00208 |
| Sonnet 5.5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
react-components 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Components
Component Structure
import { cn } from "@/lib/utils";
interface ComponentProps {
className?: string;
children: React.ReactNode;
variant?: "default" | "primary" | "secondary";
}
export function Component({
className,
children,
variant = "default",
}: ComponentProps) {
return (
<div
className={cn(
"rounded-lg bg-background p-4",
"hover:bg-muted/50 transition-colors",
{
"border-blue-500": variant === "primary",
"border-gray-300": variant === "default",
},
className
)}
>
{children}
</div>
);
}
Best Practices
We use TypeScript and Tailwind CSS. We use cn() for conditional classes, define clear
prop interfaces with sensible defaults, keep components focused and small, use
composition over inheritance, and implement proper loading and error states.
Props Pattern
interface Props {
// Required props first
id: string;
title: string;
// Optional props with defaults
className?: string;
variant?: "default" | "primary";
disabled?: boolean;
// Functions and callbacks
onClick?: () => void;
onSubmit?: (data: FormData) => Promise<void>;
// Children and render props
children?: React.ReactNode;
renderHeader?: () => React.ReactNode;
}
State Management
// Use hooks for state
const [isOpen, setIsOpen] = useState(false);
const [data, setData] = useState<Data | null>(null);
// Use useEffect for side effects
useEffect(() => {
fetchData().then(setData);
}, [dependency]);
// Custom hooks for reusable logic
const { user, loading, error } = useAuth();
Conditional Rendering
// Loading state
if (loading) return <Spinner />;
// Error state
if (error) return <ErrorMessage error={error} />;
// Empty state
if (!data.length) return <EmptyState />;
// Success state
return <DataDisplay data={data} />;
Testing
We test component rendering, user interactions, different states (loading, error, empty, success), and accessibility.
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 · 108 lines · 0 tokens per session scan A 982be497a5ee
react-components is a cursor rule published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 521 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
integration-issue-conventions
When creating or editing SuperPlane integration issue content (base or component issues), or when working in tmp/integrationspm or integration PM workflow.
cursorrules
You are using StyleSeed, a design-method engine whose goal is to make expert design judgment repeatable by coding agents, not to replace designers with aesthetic preferences. Preserve approved project choices; report unsupported choices instead of silently restyling the project's design system. PRODUCT-PRINCIPLES.md…
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
t3-stack
T3 Stack: tRPC + Prisma + NextAuth integration patterns.
react-frontend
React Frontend Execution Agent.
react-native
React Native: mobile app development, navigation, native modules.