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-dependency)<a href="https://agentmods.dev/rules/rosendolu/cursor-rules-deploy/lib-dependency"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/lib-dependency/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-dependency"><img src="https://agentmods.dev/badge/rules/rosendolu/cursor-rules-deploy/lib-dependency.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.00864 | $0.00864 |
| Opus 5.5 | $0.00346 | $0.00346 |
| Sonnet 5.5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
lib-dependency 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Library Version and Feature Constraints
Critical Rules
- Node.js version must be >= 22.14.0 as specified in package.json
- Use exact versions of dependencies as specified in package.json
- Follow library-specific best practices and patterns
- Handle version-specific features gracefully
- Document any version-specific changes
- Test compatibility when upgrading dependencies
Core Dependencies
CLI and Interactive Libraries
-
@inquirer/prompts(^7.4.1)- Use for interactive command-line prompts
- Import individual functions directly from package
- Utilize TypeScript types for better type safety
- Handle errors gracefully with try/catch
-
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
- Import as ESM module
- Use with Logger class for consistent styling
-
ora(^8.0.1)- Use for loading spinners
- Implement with async operations
- Use consistent spinner styles
File System and GitHub Operations
-
fs-extra(^11.2.0)- Prefer fs-extra methods over native fs
- Use promise-based API
- Utilize built-in error handling
-
globby(^14.1.0)- Use for file pattern matching
- Import as ESM module
- Utilize TypeScript types
-
@octokit/rest(^21.1.1)- Use for GitHub API operations
- Handle rate limiting gracefully
- Utilize TypeScript types
-
degit(^2.8.4)- Use for copying templates
- Handle errors appropriately
- Implement with async/await
Development Tools
-
eslint(^8.57.1)- Follow project's ESLint configuration
- Address all ESLint warnings and errors
-
prettier(^3.2.5)- Maintain consistent code formatting
- Use project's Prettier configuration
-
typescript(^5.4.2)- Use latest TypeScript features
- Follow strict type checking
- Utilize path aliases for imports
-
tsx(^4.7.1)- Use for running TypeScript files directly
- Utilize for development and testing
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 · 137 lines · 864 tokens per session scan A 3a3cfb3b8bd4
lib-dependency is a cursor rule published in the GitHub repository rosendolu/cursor-rules-deploy (37 stars, last pushed 1y ago), licensed MIT. It adds 864 tokens to every session, about $0.0035 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).