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/genuschristellaoverhang846/agent-rules-kit/agent-rulesgit clone --depth 1 https://github.com/genuschristellaoverhang846/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 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.
This is a copy
100% identical to agent-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2d ago First seen · 7 lines · 33 tokens per session scan A 502c2ec4df2b
agent-rules is a cursor rule published in the GitHub repository genuschristellaoverhang846/agent-rules-kit (1 stars, last pushed 3d 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. It is 100% identical to agent-rules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
skill-conventions
Conventions every pro-workflow skill follows - invocation intent, write semantics, buckets, and sync. A skill that gets these wrong misfires, duplicates state, or hides from the people who need it.
module-shape
Prefer modules with a narrow public surface and a thick internal implementation. Inject external dependencies at the boundary. Mock only at system edges.
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
communication-style
Communication preferences - concise responses, action-oriented, no filler, acknowledge mistakes.
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
quality-gates
Enforce quality checks before commits - lint, typecheck, and test affected code.