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/madebyaris/rakitui-aiWrote 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/madebyaris/rakitui-ai/security-best-practices)<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/security-best-practices"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/security-best-practices.svg" alt="Measured on agentmods" 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.00315 |
| Opus 5 | $0.00000 | $0.00158 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
security-best-practices 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 6d 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
Security Best Practices
This rule outlines security considerations for the Rakit UI AI project.
Input Validation
All user inputs must be validated before processing:
- Design names should be sanitized to prevent XSS
- HTML content should be validated and sanitized
- File paths should be validated to prevent directory traversal
CSRF Protection
For the design selection endpoint in src/tools/utils/serverUtils.ts:
- Implement CSRF tokens for POST requests
- Validate origin headers
- Use SameSite cookie attributes
HTML Sanitization
When handling design HTML in src/tools/templates/designSelection.ts:
- Use a library like DOMPurify for sanitization
- Whitelist allowed HTML tags and attributes
- Remove potentially dangerous elements (script, iframe, etc.)
Rate Limiting
Implement rate limiting to prevent abuse:
- Limit requests per IP address
- Limit concurrent sessions
- Add exponential backoff for repeated requests
Authentication & Authorization
For future enhancements:
- Consider adding optional authentication
- Implement session management
- Add role-based access control for private designs
Security Headers
Add security headers to all HTTP responses:
- Content-Security-Policy
- X-Frame-Options
- X-Content-Type-Options
- Strict-Transport-Security
Logging & Monitoring
- Log security-relevant events
- Monitor for suspicious patterns
- Implement alerting for security incidents
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.
- 6d ago First seen · 58 lines · 0 tokens per session scan A c0ba41a29acb
security-best-practices is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 315 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 cursor rules, from other repositories
AIRules
NexusLink MCP four-step workflow and prohibitions (copy to project .cursor/rules/ and fill the project-specific section).
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.