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/saitarrun/devforge-ai/dependency-managementnpx skills add saitarrun/Devforge-ai --skill dependency-managementgit clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/saitarrun/devforge-ai/dependency-management)<a href="https://agentmods.dev/skills/saitarrun/devforge-ai/dependency-management"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/dependency-management.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 | $0.00047 | $0.00460 |
| Opus 5 | $0.00023 | $0.00230 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
dependency-management 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 3d 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.
What it actually says
Skill: Dependency Management
Stay current. Stay secure. Minimize version mismatch.
Version Updates
Semantic Versioning:
1.0.0→2.0.0: Breaking change (test, update code)1.0.0→1.1.0: New feature (backward-compatible, usually safe)1.0.0→1.0.1: Bug fix (safe to update)
Security Patch Strategy
# 1. Check for vulnerabilities
npm audit # or pip check, cargo audit
# 2. Update vulnerable packages
npm update [email protected]
# 3. Test changes
npm test
# 4. Commit & push
git commit -m "fix(deps): update lodash to patch CVE-2021-23337"
Transitive Dependency Hell
app → [email protected]
app → [email protected]
app → [email protected]
requests → [email protected] # Different version!
Solution: Lock files (requirements.txt, package-lock.json, Cargo.lock)
Monorepo Dependencies
Shared dependencies (lock once):
root/
Cargo.lock # All crates use this
crates/
auth/
api/
db/
Deprecation Tracking
# Checklist when you deprecate something
- [ ] Announce (email, docs, header warning)
- [ ] Timeline (6 months warning)
- [ ] Alternatives (what should users use?)
- [ ] Test (ensure new way works)
- [ ] Remove (after timeline)
Status: Ready for dependency work
Best for: Version updates, security patches, CVE management
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.
- 3d ago First seen · 73 lines · 47 tokens per session scan A e7610bcf92dc
dependency-management is a skill published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 47 tokens to every session and 460 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 skills, from other repositories
iso-24495-2
Sector-specific Plain Language standard for legal communication (ISO 24495-2:2025). Applied during contract drafting, license review, and legal/compliance writing.
feature-done
Run the end-of-feature gate across checks, project conventions, change-spec compliance, current truth, and the delivery receipt.
motherduck-security-governance
Explain MotherDuck security, governance, and access-control patterns. Use for any question about SOC 2, GDPR, compliance, data residency, regions, SSO, service accounts, token handling, tenant isolation, sharing boundaries, snapshots and recovery, or governance posture — including when a securitycomplianceowner…
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.