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/coderdeltalan/agent-rules-kit/agent-rulesgit clone --depth 1 https://github.com/CoderDeltaLAN/agent-rules-kitWhat 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.00033 | $0.00033 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00007 | $0.00007 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
agent-rules 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-rules — 100% identical, 0 lines differ
What it actually says
Read relevant files before editing. Keep changes small and run local checks before committing.
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.
- yesterday First seen · 7 lines · 33 tokens per session scan A 502c2ec4df2b
agent-rules is a cursor rule published in the GitHub repository CoderDeltaLAN/agent-rules-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session, about $0.0002 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-rules
Cursor rule "project-rules" from peva3/anchor, covering cursor ai rules, core directives, critical enforcements, pre-commit checklist and required folders.
cursorrules
Senior Python engineer (18+ years). Production-quality code following AurigaIT standards.
python-core
Core Python standards — always active for all Python files.
python-security
Security rules — always active for all Python files.
python-testing
Testing standards — auto-attached to test files.
project
Project cursor rules.