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/girijashankarj/cursor-handbook/dependency-managementgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/dependency-management)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/dependency-management"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/dependency-management.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.1 | $0.00350 | $0.00350 |
| Opus 5 | $0.00175 | $0.00175 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
dependency-management 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 Management Rules
Package Manager: {{CONFIG.techStack.packageManager}}
Adding Dependencies
- Always specify exact versions in production
- Review package before adding: size, maintenance, license, security
- Prefer packages with: >1000 GitHub stars, active maintenance, TypeScript support
- Check for known vulnerabilities before adding
- Document why each major dependency was chosen
Dependency Categories
| Type | File Section | Example |
|---|---|---|
| Production | dependencies |
express, zod, prisma |
| Development | devDependencies |
jest, eslint, typescript |
| Peer | peerDependencies |
react (for libraries) |
Internal Packages
- Prefix:
{{CONFIG.packages.internalPrefix}} - Version: Follow semver strictly
- Registry:
{{CONFIG.packages.registryUrl}} - Document public API changes in CHANGELOG
Security
- Run
npm audit/pip auditweekly and in CI - No critical or high vulnerabilities allowed in production
- Automated dependency updates via Dependabot or Renovate
- Review all dependency update PRs before merging
- Pin transitive dependencies when security requires it
Update Strategy
- Patch updates: Auto-merge after CI passes
- Minor updates: Review changelog, merge within 1 week
- Major updates: Evaluate breaking changes, plan migration
- Security updates: Apply within 24 hours for critical
Bundle Size
- Monitor bundle size in CI pipeline
- Set size budgets for frontend packages
- Use tree-shaking-compatible packages
- Prefer packages that support ESM
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 · 48 lines · 350 tokens per session scan A c7d15b4d2d19
dependency-management is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 6d ago), licensed MIT. It adds 350 tokens to every session, about $0.0018 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-09-03.
Other cursor rules, from other repositories
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
new_features
Guidelines for integrating new features into the Task Master CLI.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.