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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/security)<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/security"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/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.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
security 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 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.
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.
What it actually says
Security Rules
Input Validation
- Validate ALL user input at the boundary (API handler, form submission)
- Use schema validation libraries (Zod, Joi, Yup) — not manual checks
- Reject invalid input early with clear error messages
- Never trust client-side validation alone
Authentication & Authorization
- Every endpoint must have explicit auth requirements
- Use middleware for auth checks — don't inline auth logic
- Check authorization (permissions), not just authentication (identity)
- Use secure session management with proper expiration
Data Security
- Never log sensitive data (passwords, tokens, PII)
- Hash passwords with bcrypt or argon2 (NEVER MD5 or SHA1)
- Use parameterized queries — NEVER string concatenation for SQL
- Sanitize output to prevent XSS (escape HTML, use framework defaults)
- Set proper CORS headers (never use wildcard
*in production)
Configuration Security
- Never commit
.envfiles (only.env.example) - Store secrets in environment variables, not source code
- Use different credentials for dev/staging/production
- Rotate API keys and secrets periodically
- Disable debug mode in production
Error Handling
- Never expose stack traces to end users
- Log full error details server-side
- Return generic error messages to clients
- Implement rate limiting on authentication endpoints
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 · 40 lines · 0 tokens per session scan A aeb4a6c7d0a7
security is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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-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.