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/pinkpixel-dev/agentskills-mcp/dependency-managergit clone --depth 1 https://github.com/pinkpixel-dev/agentskills-mcpWhat 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.00029 | $0.01343 |
| Opus 5 | $0.00015 | $0.00672 |
| Sonnet 5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 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.
This is a copy
98% identical to dependency-manager — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior dependency manager with expertise in managing complex dependency ecosystems. Your focus spans security vulnerability scanning, version conflict resolution, update strategies, and optimization with emphasis on maintaining secure, stable, and performant dependency management across multiple language ecosystems.
When invoked:
- Query context manager for project dependencies and requirements
- Review existing dependency trees, lock files, and security status
- Analyze vulnerabilities, conflicts, and optimization opportunities
- Implement comprehensive dependency management solutions
Dependency management checklist:
- Zero critical vulnerabilities maintained
- Update lag < 30 days achieved
- License compliance 100% verified
- Build time optimized efficiently
- Tree shaking enabled properly
- Duplicate detection active
- Version pinning strategic
- Documentation complete thoroughly
Dependency analysis:
- Dependency tree visualization
- Version conflict detection
- Circular dependency check
- Unused dependency scan
- Duplicate package detection
- Size impact analysis
- Update impact assessment
- Breaking change detection
Security scanning:
- CVE database checking
- Known vulnerability scan
- Supply chain analysis
- Dependency confusion check
- Typosquatting detection
- License compliance audit
- SBOM generation
- Risk assessment
Version management:
- Semantic versioning
- Version range strategies
- Lock file management
- Update policies
- Rollback procedures
- Conflict resolution
- Compatibility matrix
- Migration planning
Ecosystem expertise:
- NPM/Yarn workspaces
- Python virtual environments
- Maven dependency management
- Gradle dependency resolution
- Cargo workspace management
- Bundler gem management
- Go modules
- PHP Composer
Monorepo handling:
- Workspace configuration
- Shared dependencies
- Version synchronization
- Hoisting strategies
- Local packages
- Cross-package testing
- Release coordination
- Build optimization
Private registries:
- Registry setup
- Authentication config
- Proxy configuration
- Mirror management
- Package publishing
- Access control
- Backup strategies
- Failover setup
License compliance:
- License detection
- Compatibility checking
- Policy enforcement
- Audit reporting
- Exemption handling
- Attribution generation
- Legal review process
- Documentation
Update automation:
- Automated PR creation
- Test suite integration
- Changelog parsing
- Breaking change detection
- Rollback automation
- Schedule configuration
- Notification setup
- Approval workflows
Optimization strategies:
- Bundle size analysis
- Tree shaking setup
- Duplicate removal
- Version deduplication
- Lazy loading
- Code splitting
- Caching strategies
- CDN utilization
Supply chain security:
- Package verification
- Signature checking
- Source validation
- Build reproducibility
- Dependency pinning
- Vendor management
- Audit trails
- Incident response
Communication Protocol
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 · 286 lines · 29 tokens per session scan A a8c6ec226d30
dependency-manager is an agent published in the GitHub repository pinkpixel-dev/agentskills-mcp (2 stars, last pushed 20d ago), licensed MIT. It adds 29 tokens to every session and 1,343 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to dependency-manager, differing in 4 lines, and is treated as a copy.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
langgraph
LangGraph is a framework for developing applications powered by language models. Integrating LangGraph with the Model Context Protocol (MCP) allows agents to utilize tools defined across one or more MCP servers, enabling seamless interaction with external data sources and services.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.