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/sonatype/sonatype-cursor-plugin/dependency-hygienegit clone --depth 1 https://github.com/sonatype/sonatype-cursor-pluginWhat 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.00000 | $0.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
dependency-hygiene 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.
What it actually says
Dependency hygiene
When editing dependency files:
-
Adding new dependencies: Before adding a new dependency, consider running
/check-dependency <package>to verify its security posture, license compatibility, and quality metrics. -
Updating versions: When changing dependency versions, use
/find-safer-version <package>to find the most secure version that meets your requirements. -
Version pinning: Prefer exact versions over ranges to ensure reproducible builds. Avoid:
*orlatest(unpredictable)^or~ranges in production (can introduce vulnerabilities)
-
Periodic audits: Run
/audit-dependenciesregularly to catch newly disclosed vulnerabilities in existing dependencies. -
PURL format reference:
- npm:
pkg:npm/<name>@<version> - Maven:
pkg:maven/<groupId>/<artifactId>@<version> - PyPI:
pkg:pypi/<name>@<version> - Go:
pkg:golang/<module>@<version>
- npm:
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 · 36 lines · 0 tokens per session scan A 7c2bbb617eb5
dependency-hygiene is a cursor rule published in the GitHub repository sonatype/sonatype-cursor-plugin (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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.