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/asgarovf/locusai/dependency-managernpx skills add asgarovf/locusai --skill dependency-managergit clone --depth 1 https://github.com/asgarovf/locusaiWrote 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/skills/asgarovf/locusai/dependency-manager)<a href="https://agentmods.dev/skills/asgarovf/locusai/dependency-manager"><img src="https://agentmods.dev/badge/skills/asgarovf/locusai/dependency-manager.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.00035 | $0.01048 |
| Opus 5 | $0.00017 | $0.00524 |
| Sonnet 5 | $0.00007 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade B, and why
dependency-manager scanned grade B with 1 finding 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 5d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules package-lock.json Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Manager
When to use this skill
- Updating outdated dependencies
- Fixing security vulnerability alerts (Dependabot, npm audit)
- Resolving dependency conflicts or version mismatches
- Adding new packages (choosing the right ones)
- Cleaning up unused dependencies
- Migrating between package managers
Step 1: Assess current state
Node.js / npm / yarn
# Check for outdated packages
npm outdated
yarn outdated
# Security audit
npm audit
yarn audit
# List installed packages
npm ls --depth=0
npm ls <package-name> # Check specific package tree
# Find unused dependencies
npx depcheck
Python / pip
# Check outdated
pip list --outdated
# Security audit
pip-audit
safety check
# Show dependency tree
pipdeptree
Step 2: Update strategy
Semantic versioning guide
MAJOR.MINOR.PATCH
^2.1.0 → allows 2.x.x (minor + patch updates)
~2.1.0 → allows 2.1.x (patch updates only)
2.1.0 → exact version (no updates)
Safe update order
-
Patch updates first — bug fixes, lowest risk:
npm update # Updates within semver range -
Minor updates — new features, backward compatible:
npx npm-check-updates --target minor -u npm install npm test -
Major updates — one at a time, may have breaking changes:
npm install <package>@latest # Read CHANGELOG/migration guide # Run tests # Fix breaking changes # Commit
Step 3: Handle vulnerabilities
# View audit details
npm audit
# Auto-fix where possible
npm audit fix
# Force fix (may include breaking changes — review carefully)
npm audit fix --force
# If a vulnerability is in a transitive dependency:
# 1. Check if parent package has a newer version
npm ls <vulnerable-package>
# 2. Override the transitive version
# In package.json:
{
"overrides": {
"vulnerable-package": "^2.0.1"
}
}
Step 4: Resolve conflicts
Peer dependency conflicts
# See the conflict
npm install --dry-run
# Option 1: Use --legacy-peer-deps (temporary)
npm install --legacy-peer-deps
# Option 2: Fix by aligning versions
# Read both packages' peerDependencies and find compatible range
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.
- 5d ago First seen · 193 lines · 35 tokens per session scan B 264080549aeb
dependency-manager is a skill published in the GitHub repository asgarovf/locusai (23 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,048 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dependency-audit
依赖漏洞审计。适用于 npm、yarn、pnpm、lockfile、本地目录和远程 Git 仓库的依赖风险审计场景;前端项目的依赖漏洞审计优先使用 locklens。.
dep-audit
Audit and update project dependencies: find outdated packages, check for vulnerabilities, auto-update safely with lockfile regeneration.
upgrade-packages-js
Safely upgrade JavaScript packages with breaking change detection, migration guidance, and automated code migrations (npm/pnpm/yarn). Cross-platform with git safety branch enforcement.
audit-full
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing. Loads entire codebases for cross-file pattern detection and generates structured audit reports with severity-ranked findings. Use when you need whole-project analysis…
depsguard
Install and run DepsGuard, a zero-dependency CLI that scans and fixes package manager configs (npm, pnpm, yarn, bun, uv) for supply chain security best practices.
tauri-django-react
Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.