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/josemurilors/abnt-mcp/cursorrulesgit clone --depth 1 https://github.com/josemurilors/ABNT-MCPWhat 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.01112 | $0.01112 |
| Opus 5 | $0.00556 | $0.00556 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
cursorrules scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer ${API_TOKEN}" https://api.example.com How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
============================================
Cursor Rules - Vibe Coding Security
============================================
--------------------------------------------
CRITICAL: Secrets Management Rules
--------------------------------------------
NEVER DO:
- Never hardcode API keys, tokens, passwords, or secrets in source code
- Never commit .env files with real credentials
- Never log sensitive information (API keys, tokens, passwords)
- Never include secrets in error messages or stack traces
- Never use placeholder secrets like "test_key_123" that look real
- Never create inline credentials in scripts or config files
ALWAYS DO:
- Always use environment variables for secrets: os.getenv (Python)
- Always reference .env.example for required environment variables
- Always use GitHub Secrets for CI/CD credentials
- Always use secret managers in production (AWS Secrets Manager, HashiCorp Vault, Infisical)
- Always validate that required env vars exist at startup
- Always use different credentials per environment (dev, staging, production)
--------------------------------------------
Code Generation Rules
--------------------------------------------
Environment Variables Pattern (Python):
# CORRECT
import os
api_key = os.getenv('OPENAI_API_KEY')
if not api_key:
raise ValueError('OPENAI_API_KEY is required')
# WRONG
api_key = 'sk-proj-abc123...'
Environment Variables Pattern (Shell):
# CORRECT
curl -H "Authorization: Bearer ${API_TOKEN}" https://api.example.com
# WRONG
curl -H "Authorization: Bearer sk-proj-abc123..." https://api.example.com
--------------------------------------------
File Creation Rules
--------------------------------------------
When creating new files:
- Always add .env, .env.*, *.key, *.pem to .gitignore
- Always create .env.example with placeholder values
- Never create files named credentials.json, secrets.json, service-account.json
- Never create .cursor/ or .clinerules/ directories with sensitive data
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.
- yesterday First seen · 147 lines · 1,112 tokens per session scan A 0c8f0256ac24
cursorrules is a cursor rule published in the GitHub repository josemurilors/ABNT-MCP (0 stars, last pushed 28d ago), licensed MIT. It adds 1,112 tokens to every session, about $0.0056 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.