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/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/security-compliance)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/security-compliance"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/security-compliance/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/girijashankarj/cursor-handbook/security-compliance"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/security-compliance.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.00394 | $0.00394 |
| Opus 5 | $0.00197 | $0.00197 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
security-compliance 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 Compliance Rules
Data Classification
| Level | Examples | Handling |
|---|---|---|
| Public | Marketing content, docs | No restrictions |
| Internal | Business logic, configs | Access controls required |
| Confidential | User data, financials | Encryption required |
| Restricted | PII, credentials, keys | Encryption + audit logging |
Compliance Requirements
Data in Transit
- ALWAYS use TLS/HTTPS for all external communication
- Minimum TLS 1.2, prefer TLS 1.3
- Certificate pinning for mobile clients
- Encrypt internal service-to-service communication
Data at Rest
- Encrypt all database storage (AES-256)
- Encrypt backups and snapshots
- Use envelope encryption for sensitive fields
- Secure key management via {{CONFIG.techStack.cloud}} KMS
Data Retention
- Define retention periods for all data types
- Implement automated data purging
- Soft delete with configurable hard delete schedule
- Audit log retention: minimum 1 year
API Security
- OAuth 2.0 / OpenID Connect for authentication
- API key rotation every 90 days
- Rate limiting on all endpoints
- Request size limits
- CORS configuration — allowlist only trusted origins
- Security headers: CSP, HSTS, X-Frame-Options, X-Content-Type-Options
Dependency Security
- Run
npm audit/pip auditin CI pipeline - No dependencies with known critical vulnerabilities
- Pin dependency versions in production
- Review transitive dependencies quarterly
Incident Response
- Log all security-relevant events
- Alert on: failed auth attempts (>5), privilege escalation, data export anomalies
- Maintain incident response runbook
- Post-incident review within 48 hours
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 · 55 lines · 394 tokens per session scan A 5204ec0de946
security-compliance is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 10d ago), licensed MIT. It adds 394 tokens to every session, about $0.0020 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-09-03.
Other cursor rules, from other repositories
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
new_features
Guidelines for integrating new features into the Task Master CLI.
utilities
// ✅ DO: Create focused, reusable utilities /.
commands
Guidelines for implementing CLI commands using Commander.js.