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 rules/owasp/docksec/cursorrulesgit clone --depth 1 https://github.com/OWASP/DockSecWhat 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.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
cursorrules 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 2d 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
DockSec Cursor Rules
- STRICT: NEVER use "Cursor Agent", "AI Coding Assistant", or any AI-specific branding in code, comments, documentation, or commit messages.
- STRICT: NEVER add "Co-authored-by: Cursor" or any AI attribution to git commit messages. This is a hard requirement for project integrity.
- All code and comments must be professional, human-centric, and focused strictly on project functionality.
- Do not use em-dashes; use normal hyphens only.
- Do not use emojis in any communication or code.
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.
- 2d ago First seen · 8 lines · 112 tokens per session scan A 163533b6604d
cursorrules is a cursor rule published in the GitHub repository OWASP/DockSec (476 stars, last pushed 12d ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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-30.
Other cursor rules, from other repositories
cursorrules
You are a coding assistant for this repository. Use the memory server for persistent context and follow the instructions in CLAUDE.md and AGENTS.md.
ai-safe2-sovereign
AI SAFE2 v3.0 Sovereign Security Rules for Cursor.
cursorrules
Always run the following before any task.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.