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/projectgit 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.00123 | $0.00123 |
| Opus 5 | $0.00062 | $0.00062 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
project 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
Client engagement platform — Cursor Rules
Project-wide Cursor rules generated by EmbedIQ. Path-scoped rules in this same directory add language- and compliance-specific guidance automatically.
Stack
- Languages: typescript
- Build: npm
- Testing: jest
Ground rules
- Run tests before committing; never commit code that fails tests.
- Keep changes scoped to the task; avoid drive-by refactors.
- Prefer editing existing files over creating new ones.
- Never hardcode secrets, API keys, or credentials.
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 · 20 lines · 123 tokens per session scan A 19bdeaedbea3
project is a cursor rule published in the GitHub repository asq-sheriff/embediq (5 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session, about $0.0006 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.
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…
project
Project conventions - canonical source is AGENTS.md.
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.