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/jlevy/repren/general-comment-rulesgit clone --depth 1 https://github.com/jlevy/reprenWhat 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.00012 | $0.00012 |
| Opus 5 | $0.00006 | $0.00006 |
| Sonnet 5 | $0.00002 | $0.00002 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
general-comment-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- general-comment-rules — 100% identical, 0 lines differ
What it actually says
../../docs/general/agent-rules/general-comment-rules.md
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 · 1 lines · 12 tokens per session scan A 24f97a93cae4
general-comment-rules is a cursor rule published in the GitHub repository jlevy/repren (374 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session, about $0.0001 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-30.
Other cursor rules, from other repositories
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
simple-language
when writing documentation.
backend-python
Cursor rule "backend-python" from coeusyk/inference-x, covering backend python rules, stack assumptions, code style, fastapi conventions and schema conventions.
smol-cli
Setup once per project: install with npm i -g @electrooo69/sped-cli@latest --force, then run sped setup --all in the project root if .sped-cli/ is missing. Never delete .sped-cli/. Only follow the instruction file for your current agent. Do not delete or modify other agents' instruction files unless explicitly asked.…
api-tester
Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations.
developer-advocate
Expert developer advocate specializing in building developer communities, creating compelling technical content, optimizing developer experience (DX), and driving platform adoption through authentic engineering engagement. Bridges product and engineering teams with external developers.