Borrowing it
Nothing to install: this file belongs to ensingm2/AI-threat-modeling-rulesets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ensingm2/AI-threat-modeling-rulesets/main/.cursorrulesgit clone --depth 1 https://github.com/ensingm2/AI-threat-modeling-rulesetsWrote 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/ensingm2/ai-threat-modeling-rulesets/cursorrules)<a href="https://agentmods.dev/rules/ensingm2/ai-threat-modeling-rulesets/cursorrules"><img src="https://agentmods.dev/badge/rules/ensingm2/ai-threat-modeling-rulesets/cursorrules/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/ensingm2/ai-threat-modeling-rulesets/cursorrules"><img src="https://agentmods.dev/badge/rules/ensingm2/ai-threat-modeling-rulesets/cursorrules.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.00945 | $0.00945 |
| Opus 5.5 | $0.00378 | $0.00378 |
| Sonnet 5.5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling Framework
Project: LLM Instruction Sets for Threat Modeling
Creator: Mike Ensing ([email protected])
⚠️ MANDATORY STARTUP SELECTIONS (BEFORE ANY WORK)
CRITICAL: You MUST ask BOTH questions before beginning Stage 1. This is absolute and non-negotiable.
Step 1: Ask BOTH Questions (USE THIS EXACT SCRIPT - MANDATORY)
Copy this prompt VERBATIM when starting a threat model:
Before we begin, I need two selections:
1. Operational Mode:
- Collaborative Mode: Active user engagement, clarifying questions, stage approvals
- Automatic Mode: Autonomous operation, reasonable assumptions, no user interaction
2. Critic Review Mode:
- With Critic Review: Each stage undergoes adversarial quality validation
- Without Critic Review (Recommended): Stages proceed directly without separate validation phases
Important Note: Critic Review mode will be especially valuable when multi-agent support is added, enabling a separate agent to perform independent validation. For single-agent runs, the benefit of self-critique is generally not worth the increase in runtime and API requests. Recommendation: Without Critic Review unless you have a specific need for it.
Please specify: [Collaborative/Automatic] and [With Critic/Without Critic]
Step 2: Load mode file and confirm
- Load
modes/collaborative-mode.mdORmodes/automatic-mode.md - Confirm BOTH selections before proceeding
Step 3: Begin Stage 1
PROHIBITED:
- ❌ Starting Stage 1 without asking about operational mode
- ❌ Starting Stage 1 without asking about critic review mode
- ❌ Assuming either preference without explicit user selection
- ❌ Asking about mode but forgetting to ask about critic review
- ❌ Using your own wording instead of the exact script above
- ❌ Asking the two questions in separate prompts (MUST be combined)
Quick Reference
- Read:
.ai-instructions/core/entry-point.md - Read:
.ai-instructions/skills/workflow-guide.md - ASK USER BOTH: Operational mode + Critic review mode (see above)
- Load:
.ai-instructions/modes/[selected-mode].md - Confirm selections
- Read ALL user-provided source files (enumerate directories, read every file - no exceptions)
- Begin Stage 1
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.
- 1mo ago First seen · 95 lines · 945 tokens per session scan A 601c17e27483
cursorrules is a cursor rule published in the GitHub repository ensingm2/AI-threat-modeling-rulesets (12 stars, last pushed 7mo ago), licensed MIT. It adds 945 tokens to every session, about $0.0038 per session on Opus 5.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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.