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/asq-sheriff/embediq/securitygit clone --depth 1 https://github.com/asq-sheriff/embediqWhat 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.00076 | $0.00076 |
| Opus 5 | $0.00038 | $0.00038 |
| Sonnet 5 | $0.00015 | $0.00015 |
| Haiku 4.5 | $0.00008 | $0.00008 |
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 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.
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
- Never hardcode secrets, API keys, passwords, or tokens.
- Never log sensitive data (PII, PHI, credentials).
- Validate all user input at system boundaries.
- Use parameterized queries for all database access.
- Follow OWASP Top 10 guidelines.
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 · 13 lines · 76 tokens per session scan A e62f8308cde2
security is a cursor rule published in the GitHub repository asq-sheriff/embediq (5 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session, about $0.0004 per session on Opus 5. 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
project
Core project context for ai-context-kit.
project
Project conventions - canonical source is AGENTS.md.
code-discipline
Coding methodology for production-grade software development. Enforces structured thinking before coding, verifying reality, simplicity, surgical changes, contract awareness, and verifiable success criteria. Use when writing, reviewing, or refactoring any code that must remain correct and maintainable past initial…
breakthrough-loop
Research discipline - breakthrough loop with a hard-to-fool harness.
shipjaw
Shipjaw continuation contract for this fixture repo.
orchestrator-main
Rules for the main orchestrator agent in multi-agent workflows.