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 skills/usrrname/cursorrules/dependency-analysis-agentnpx skills add usrrname/cursorrules --skill dependency-analysis-agentgit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00028 | $0.02528 |
| Opus 5 | $0.00014 | $0.01264 |
| Sonnet 5 | $0.00006 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
Grade A, and why
dependency-analysis 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.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Analysis
Critical Rules
- Before a dependency is installed (npm install, yarn add, pnpm add), automatically analyze the package using socket.io to get the package information from the npm registry and GitHub.
- Check maintenance frequency by examining last release date, commit activity, and issue response times
- Scan for known security vulnerabilities using npm audit and security databases
- Assess popularity through download counts, GitHub stars, and community adoption
- Provide actionable recommendations for dependency selection in a clear, actionable format with severity levels
Analysis Categories
Maintenance Frequency
- Last release date and frequency
- Recent commit activity (last 30, 90, 365 days)
- Issue response times and resolution rates
- Pull request merge frequency
- Maintainer activity and responsiveness
Security Vulnerabilities
- Known CVEs and security advisories
- Dependency tree vulnerabilities
- Outdated dependencies with security patches
- License compliance issues
- Supply chain attack risks
Popularity & Ecosystem Health
- Weekly/monthly download counts
- GitHub stars, forks, and watchers
- Community adoption and usage trends
- Documentation quality and completeness
- TypeScript support and type definitions
- Bundle size impact and performance considerations
filters:
- type: event pattern: "file_modified|file_created"
- type: user_input pattern: "analyze dependencies|npm install|yarn add|pnpm add"
- type: file_extension pattern: "\.(json|lock)$"
- type: content pattern: "(dependencies|devDependencies|peerDependencies)"
matches: | // Match package.json modifications and lock file changes package.json package-lock.json yarn.lock pnpm-lock.yaml
transforms: |
// Analyze dependencies when package files are modified
{{
const analyzeDependency = async (packageName, version) => {
try {
// Fetch package information from npm registry
const npmResponse = await fetch(https://registry.npmjs.org/${packageName});
const npmData = await npmResponse.json();
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 · 350 lines · 28 tokens per session scan A 1ad3f4545b90
dependency-analysis is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 28 tokens to every session and 2,528 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.
Remove Old Logs
Remove log files older than 1 day from logs directory.