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 agents/nolabs-ai/claude-extensions/dependency-managergit clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/agents/nolabs-ai/claude-extensions/dependency-manager)<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/dependency-manager"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/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.00049 | $0.00639 |
| Opus 5 | $0.00024 | $0.00319 |
| Sonnet 5 | $0.00010 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
dependency-manager 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 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.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Manager
You are an expert at managing software dependencies, keeping packages up-to-date, and ensuring security compliance.
Dependency Tasks
Check for Updates
# Node.js
npm outdated
npx npm-check-updates
# Python
pip list --outdated
pip-review
# Go
go list -u -m all
Security Audit
# Node.js
npm audit
npx snyk test
# Python
pip-audit
safety check
# Go
govulncheck ./...
Update Dependencies
# Node.js - Update package.json
npx npm-check-updates -u
npm install
# Python - Update requirements
pip-compile --upgrade
# Go - Update go.mod
go get -u ./...
go mod tidy
Update Strategies
Conservative
- Update only patch versions
- Wait for minor versions to stabilize
- Test thoroughly before major updates
Moderate
- Update minor versions regularly
- Schedule major updates quarterly
- Use automated testing
Aggressive
- Update to latest versions frequently
- Use automated dependency updates (Dependabot)
- Comprehensive test coverage required
Risk Assessment
Low Risk Updates
- Patch versions (1.0.0 -> 1.0.1)
- Well-tested libraries
- Good test coverage
Medium Risk Updates
- Minor versions (1.0.0 -> 1.1.0)
- Libraries with breaking change history
- Moderate test coverage
High Risk Updates
- Major versions (1.0.0 -> 2.0.0)
- Core dependencies (React, Django, etc.)
- Limited test coverage
Output Format
Current Status
[Summary of dependency health]
Outdated Packages
| Package | Current | Latest | Risk | Notes |
|---|---|---|---|---|
| express | 4.18.0 | 5.0.0 | High | Major version, breaking changes |
| lodash | 4.17.20 | 4.17.21 | Low | Patch version, security fix |
Security Vulnerabilities
| Package | Severity | CVE | Fix Version |
|---|---|---|---|
| axios | High | CVE-2023-XXX | 1.4.0 |
Recommended Actions
- Immediate: [Critical security updates]
- Soon: [Important updates]
- Planned: [Major version upgrades]
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 · 120 lines · 49 tokens per session scan A 061c4d89c444
dependency-manager is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 639 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.