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/hamzaamjad/cursor-rules/004-risk-checkpointgit clone --depth 1 https://github.com/hamzaamjad/cursor-rulesWhat 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.00008 | $0.01008 |
| Opus 5 | $0.00004 | $0.00504 |
| Sonnet 5 | $0.00002 | $0.00202 |
| Haiku 4.5 | $0.00001 | $0.00101 |
Grade B, and why
004-risk-checkpoint scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
r'sudo(?!\s+apt-get)', # Unwhitelisted sudo r'DELETE.*WHERE.*[><=].*1000', # Bulk operations How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Checkpoint
Purpose: Block operations exceeding risk thresholds. 90-95% critical incident reduction.
Risk Classification
RISK_LEVELS = {
'CRITICAL': ['data_loss', 'security_breach', 'system_corruption'],
'HIGH': ['service_disruption', 'config_damage', 'privacy_violation'],
'MEDIUM': ['performance_impact', 'reversible_changes', 'resource_usage'],
'LOW': ['read_operations', 'isolated_changes', 'logging']
}
RISK_SIGNATURES = {
'CRITICAL': [
r'rm\s+-rf\s+/', # Root deletion
r'DROP\s+DATABASE|TRUNCATE', # Data destruction
r'sudo\s+chmod\s+777', # Security compromise
r'(API_KEY|SECRET|PASSWORD)', # Credential exposure
r'(\.ssh/|/etc/passwd)', # System file mods
],
'HIGH': [
r'sudo(?!\s+apt-get)', # Unwhitelisted sudo
r'DELETE.*WHERE.*[><=].*1000', # Bulk operations
r'git\s+push.*main|master', # Direct main push
]
}
Risk Assessment Pipeline
def assess_risk(operation):
# 1. Pattern matching
base_score = match_signatures(operation, RISK_SIGNATURES)
# 2. Context multipliers
multipliers = {
'environment': 2.0 if prod else 1.0,
'bulk_operation': 1.5 if count > 100 else 1.0,
'data_sensitivity': 2.0 if has_pii else 1.0,
'time_restriction': 1.5 if off_hours else 1.0
}
# 3. Sequence analysis
if creates_dangerous_sequence(operation, history):
base_score = max(base_score, 'HIGH')
# 4. Final score
return apply_multipliers(base_score, multipliers)
Decision Framework
| Risk Level | Action | Requirements |
|---|---|---|
| CRITICAL | ❌ BLOCK | Human override + justification |
| HIGH | ⚠️ WARN | Explicit approval + safeguards |
| MEDIUM | 🔔 NOTIFY | Confirmation + logging |
| LOW | ✅ PROCEED | Log for audit |
Implementation Patterns
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 · 138 lines · 8 tokens per session scan B 112003f36b94
004-risk-checkpoint is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 1,008 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.