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.
git clone --depth 1 https://github.com/rosendolu/cursor-rules-deployWrote 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/rosendolu/cursor-rules-deploy/lib)<a href="https://agentmods.dev/rules/rosendolu/cursor-rules-deploy/lib"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/lib/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/rosendolu/cursor-rules-deploy/lib"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/lib.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00708 | $0.00708 |
| Opus 5.5 | $0.00283 | $0.00283 |
| Sonnet 5.5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
lib 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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Library Version and Feature Constraints
Required Node Version
- Node.js version must be >= 22.14.0 as specified in package.json
Core Dependencies
Use these specific versions and their features:
CLI and Utility Libraries
-
commander(^11.0.0)- Use for command-line interface implementation
- Prefer declarative command definitions
- Utilize built-in option validation
-
chalk(^5.3.0)- Use for terminal text styling
- Prefer template literals with chalk
- Use consistent color schemes for different message types
-
inquirer(^9.2.12)- Use for interactive command-line prompts
- Prefer async/await syntax with prompts
- Utilize built-in validation features
-
ora(^8.0.1)- Use for loading spinners
- Implement with async operations
- Use consistent spinner styles
File System Operations
fs-extra(^11.2.0)- Prefer fs-extra methods over native fs
- Use promise-based API
- Utilize built-in error handling
Development Tools
-
eslint(^8.56.0)- Follow project's ESLint configuration
- Address all ESLint warnings and errors
-
prettier(^3.2.5)- Maintain consistent code formatting
- Use project's Prettier configuration
Best Practices
- Always use the latest features available in the specified versions
- Prefer built-in functionality over custom implementations
- Use TypeScript types when available
- Handle version-specific features gracefully
Version Upgrade Guidelines
- Document any version-specific changes
- Test compatibility when upgrading dependencies
- Update related code when library versions change
- Maintain backward compatibility where possible
Code Examples
Command Line Interface (commander)
// Preferred
program
.name('cursor-rules-deploy')
.description('Deploy Cursor AI rules and templates')
.version('1.0.0');
// Avoid
if (process.argv.includes('--version')) {
console.log('1.0.0');
}
Logging (chalk)
// Preferred - Always use Logger class with chalk
Logger.info(chalk.blue('Processing'), chalk.green(filename));
Logger.error(chalk.red('Error:'), chalk.yellow(errorMessage));
Logger.warn(chalk.yellow('Warning:'), chalk.dim(warningMessage));
Logger.debug(chalk.gray('Debug:'), chalk.dim(debugInfo));
// Avoid
console.log('Processing', filename);
console.error('Error:', errorMessage);
console.warn('Warning:', warningMessage);
console.debug('Debug:', debugInfo);
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.
- 1mo ago First seen · 100 lines · 708 tokens per session scan A a971933e0d18
lib is a cursor rule published in the GitHub repository rosendolu/cursor-rules-deploy (37 stars, last pushed 1y ago), licensed MIT. It adds 708 tokens to every session, about $0.0028 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).