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/packtman/AI-Tools-Secure-ConfigsWrote 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/packtman/ai-tools-secure-configs/security)<a href="https://agentmods.dev/rules/packtman/ai-tools-secure-configs/security"><img src="https://agentmods.dev/badge/rules/packtman/ai-tools-secure-configs/security/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/packtman/ai-tools-secure-configs/security"><img src="https://agentmods.dev/badge/rules/packtman/ai-tools-secure-configs/security.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.00333 | $0.00333 |
| Opus 5.5 | $0.00133 | $0.00133 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade C, and why
security scanned grade C with 4 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 2mo 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 rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- When creating Docker configurations, never run as root; use non-root users. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Never execute `curl | bash`, `wget | sh`, or piped-execution patterns. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Never run `rm -rf /`, `DROP DATABASE`, `FORMAT`, or other destructive commands without explicit user confirmation. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Never execute `curl | bash`, `wget | sh`, or piped-execution patterns. What it actually says
Security Rules
Never Do
- Never read, display, log, or reference contents of
.env,.env.*, or files undersecrets/. - Never hard-code API keys, passwords, tokens, connection strings, or any credentials.
- Never execute
curl | bash,wget | sh, or piped-execution patterns. - Never run
rm -rf /,DROP DATABASE,FORMAT, or other destructive commands without explicit user confirmation. - Never modify
.ssh/,.aws/,.config/gcloud/, or other credential directories. - Never disable TLS verification, SSL checks, or certificate validation.
- Never install packages from unverified sources or arbitrary URLs.
Always Do
- Use environment variables for all secrets and configuration values.
- Validate and sanitize all user inputs in generated code.
- Use parameterized queries for database operations — never string concatenation.
- Include error handling that does not leak sensitive information.
- Follow the principle of least privilege for file permissions, IAM roles, and access grants.
- Use well-maintained, actively-supported dependencies only.
Code Generation Standards
- Add input validation to all public-facing functions.
- Use secure defaults (HTTPS, strong encryption algorithms, secure cookie flags).
- Generate code that passes common SAST tools (Semgrep, CodeQL, Bandit).
- When creating Docker configurations, never run as root; use non-root users.
- When generating CI/CD pipelines, never store secrets in plain text; use the platform's secrets mechanism.
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.
- 2mo ago First seen · 35 lines · 333 tokens per session scan C 0bff060d3018
security is a cursor rule published in the GitHub repository packtman/AI-Tools-Secure-Configs (4 stars, last pushed 14d ago), licensed MIT. It adds 333 tokens to every session, about $0.0013 per session on Opus 5.5. A static security scan graded it C with 4 findings (asks for root, downloads and executes remote code, recursive force delete). 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
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.