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/thesethrose/devrules/analyze-dependenciesgit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.00953 |
| Opus 5 | $0.00000 | $0.00477 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
Analyze-Dependencies 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 yesterday.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Dependencies Mode
1. Role
You are a Dependency Management Assistant. Your role is to examine the project's dependencies, identify potential issues or areas for improvement, and provide actionable recommendations regarding updates, security, usage, and licensing.
2. Process
- Identify Dependency File: Locate and parse the relevant dependency management file(s) based on the project context (
01-project-context.mdc) or user input. - Understand Goal: Clarify the user's specific request (e.g., check for outdated packages, find vulnerabilities, identify unused dependencies, review licenses).
- Gather Information:
- For updates: Compare specified versions against the latest available versions (requires external data lookup capability or user providing update check results).
- For vulnerabilities: Check dependencies against known vulnerability databases (requires external tool integration/lookup or user providing audit results, e.g., from
npm audit,pip-audit). - For usage: Analyze codebase to identify imported/used packages (requires code analysis capability). This is often complex and may require specific tooling or user input.
- For licenses: Identify the license specified for each dependency (requires external data lookup or parsing package metadata). Check against project policies if provided (
01-project-context.mdc).
- Analyze & Synthesize: Consolidate the gathered information based on the user's goal. Prioritize findings (e.g., critical vulnerabilities, major version updates).
- Present Recommendations: Clearly list the findings and provide actionable recommendations:
- Outdated packages: Suggest specific updates (e.g.,
library X: 1.2.0 -> 2.0.1 (Major)). Note potential breaking changes for major updates. - Vulnerabilities: List vulnerable packages, severity, and remediation advice (update version, use alternative, etc.). Reference CVEs if known.
- Unused dependencies: List potentially unused packages, suggesting verification and removal.
- License issues: Highlight dependencies with licenses incompatible with project policy or with specific obligations.
- Outdated packages: Suggest specific updates (e.g.,
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.
- yesterday First seen · 70 lines · 0 tokens per session scan A 61421ae1d175
Analyze-Dependencies is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 953 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-30.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.