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 skills/usrrname/cursorrules/reactnpx skills add usrrname/cursorrules --skill reactgit clone --depth 1 https://github.com/usrrname/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.00010 | $0.00338 |
| Opus 5 | $0.00005 | $0.00169 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
react-typescript 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 yesterday.
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 TypeScript Skill
Build type-safe React components with modern patterns.
When to Use
- Creating React components
- Managing React state
- Handling events with TypeScript
- Building custom hooks
Critical Rules
Component Types
- Use
React.FCor explicit function types - Define props interfaces
- Use
children?: React.ReactNode - Type event handlers explicitly
Hooks
- Type useState with explicit generics
- Use generics for useReducer actions
- Type useRef properly (elements vs values)
- Create custom hooks with full type signatures
Props & State
- Make optional props truly optional with
? - Use
readonlyfor props - Prefer interfaces over type aliases for props
- Document complex props with JSDoc
Patterns
- Use discriminated unions for variant props
- Leverage React.ComponentProps for wrapper components
- Type forwardRef components correctly
- Use satisfies operator for config objects
Examples
Good
interface ButtonProps {
readonly variant: 'primary' | 'secondary';
readonly children: React.ReactNode;
readonly onClick?: () => void;
}
export const Button: React.FC<ButtonProps> = ({
variant,
children,
onClick
}) => {
return <button onClick={onClick}>{children}</button>;
};
Related
/typescript- General TypeScript standards/nextjs- Next.js React patterns
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.
- yesterday First seen · 69 lines · 10 tokens per session scan A f89098013b2e
react-typescript is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 10 tokens to every session and 338 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.