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/jakerains/citrusrules/citrusrules-projectgit clone --depth 1 https://github.com/jakerains/CitrusRulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/jakerains/citrusrules/citrusrules-project)<a href="https://agentmods.dev/rules/jakerains/citrusrules/citrusrules-project"><img src="https://agentmods.dev/badge/rules/jakerains/citrusrules/citrusrules-project.svg" alt="Measured on agentmods" height="20"></a>What 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.01404 | $0.01404 |
| Opus 5 | $0.00702 | $0.00702 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
citrusrules-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CitrusRules Project Context
What This Project Is
CitrusRules is a CLI tool that fetches .mdc template files from GitHub and installs them into .cursor/rules directories. It's designed to help developers quickly set up Cursor AI rules for different development best practices.
- Package Name:
citrusrules - Current Version: 1.8.2
- GitHub: https://github.com/jakerains/citrusrules
- NPM: https://www.npmjs.com/package/citrusrules
- Author: jakerains
Project Structure
citrusrules/
├── bin/cli.js # CLI entry point with Commander.js
├── src/
│ ├── config.js # GitHub template URL configuration
│ └── utils.js # Core functionality (fetch & write templates)
├── templates/ # Source .mdc templates (13 total)
│ ├── mobile-standards.mdc # Comprehensive Expo/RN 2025 standards
│ ├── playwright-testing.mdc # Playwright testing with MCP browser tools
│ ├── performance.mdc # Performance optimization standards
│ ├── testing-strategy.mdc # Testing best practices
│ ├── TODO-tracking.mdc # TODO management system
│ └── ... (8 more templates)
├── test/ # Vitest test suite
└── .cursor/rules/ # Local rules for this project
Available Templates & CLI Flags
-d, --development-workflow→ Development workflow best practices-e, --error-handling→ Error handling patterns-p, --playwright-testing→ Playwright testing best practices with MCP browser tools--pe→ Performance optimization standards (multi-character flag)-s, --security→ Security best practices-a, --api-design→ API design standards-c, --component-standards→ Component architecture-b, --db-best-practices→ Database best practices-o, --devops-ci-cd→ DevOps and CI/CD workflows-m, --mobile-standards→ Comprehensive Expo & React Native 2025 standards (recently rewritten)-t, --TODO-tracking→ TODO management system-r, --testing-strategy→ Testing methodologies-u, --uv-python-projects→ Python project standards with uv
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.
- 4d ago First seen · 129 lines · 1,404 tokens per session scan A 5bd6732af74c
citrusrules-project is a cursor rule published in the GitHub repository jakerains/CitrusRules (2 stars, last pushed 1y ago), licensed MIT. It adds 1,404 tokens to every session, about $0.0070 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.