security-best-practices

security-best-practices is a cursor rule for Cursor from madebyaris/rakitui-ai. It costs 0 tokens per session (315 once invoked), scanned A, original, MIT.

A set of security rules for the Rakit UI AI project, covering input checks, browser-request protection, HTML cleaning, rate limits, and access control.

In plain words
What is it for?
Use it when building or reviewing design selection features, especially input handling, HTML output, sessions, and server endpoints.
Why use it?
It identifies common ways user input, generated HTML, files, sessions, and endpoints could be abused or expose the project to attacks.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when building or reviewing design selection features, especially input handling…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/madebyaris/rakitui-ai/security-best-practices
Install

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.

Clone the repo
git clone --depth 1 https://github.com/madebyaris/rakitui-ai

Made for: Cursor.

Wrote 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.

agentmods badge for security-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/security-best-practices.svg)](https://agentmods.dev/rules/madebyaris/rakitui-ai/security-best-practices)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash c0ba41a29acb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.cursor/rules/security-best-practices.mdc · 58 lines

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
Changes

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.

  1. 6d ago First seen · 58 lines · 0 tokens per session scan A c0ba41a29acb

Subscribe to this mod's changes

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.