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/mordilion/ai-instructions-and-promptsWrote 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/mordilion/ai-instructions-and-prompts/security)<a href="https://agentmods.dev/rules/mordilion/ai-instructions-and-prompts/security"><img src="https://agentmods.dev/badge/rules/mordilion/ai-instructions-and-prompts/security.svg" alt="Measured on agentmods" 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.00000 | $0.00518 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade B, and why
security scanned grade B with 2 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 7d 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.
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**: `curl | bash`. 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**: `curl | bash`. What it actually says
Bash Security
Scope: Bash/shell-specific security.
Extends: General security rules
Applies to:*.sh, *.bash, *.zsh, *.ksh, *.bats
1. Input Handling
- ALWAYS: Treat all inputs as untrusted (args, env vars, files, command output).
- ALWAYS: Validate paths, flags, and required values early. Return exit code
2on invalid usage. - ALWAYS: Quote expansions to prevent globbing and word-splitting injection.
2. Command Execution
- NEVER: Use
evalon untrusted input. - NEVER:
source/.untrusted files. - ALWAYS: Prefer arrays for command + args when constructing invocations.
- ALWAYS: Use full paths or verify commands via
command -vwhen running in controlled environments (CI, provisioning).
3. Filesystem Safety
- ALWAYS: Use
mktempfor temp files/dirs; clean up withtrap. - ALWAYS: Set safe permissions when writing secrets or artifacts (
umask 077when appropriate). - ALWAYS: Use
--to end option parsing for commands that support it (avoid “filename starts with dash” issues).
4. Secrets
- NEVER: Print secrets to stdout/stderr or logs.
- NEVER: Enable
set -xin scripts handling secrets (or ensure it is disabled around secret operations). - ALWAYS: Prefer env vars, secret stores, or injected files with restricted permissions.
5. Downloads & Supply Chain
- NEVER:
curl | bash. - ALWAYS: Pin versions and verify integrity (checksums/signatures) for downloaded artifacts.
- ALWAYS: Prefer HTTPS; fail on HTTP and handle redirects intentionally.
6. Privilege & Environment
- ALWAYS: Minimize
sudousage; scope it to the smallest possible commands. - ALWAYS: Sanitize/avoid trusting
PATHin privileged scripts; consider setting a safePATH.
Follow the general security rules; the rules above are additive.
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.
- 7d ago First seen · 45 lines · 0 tokens per session scan B 36274379781d
security is a cursor rule published in the GitHub repository mordilion/ai-instructions-and-prompts (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 tokens. A static security scan graded it B with 2 findings (downloads and executes remote code, 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
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.
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.