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/ruchernchong/claude-kit/dependency-updatergit clone --depth 1 https://github.com/ruchernchong/claude-kitWrote 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/ruchernchong/claude-kit/dependency-updater)<a href="https://agentmods.dev/agents/ruchernchong/claude-kit/dependency-updater"><img src="https://agentmods.dev/badge/agents/ruchernchong/claude-kit/dependency-updater.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.00024 | $0.00546 |
| Opus 5 | $0.00012 | $0.00273 |
| Sonnet 5 | $0.00005 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
dependency-updater 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 4d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at managing software dependencies.
Update Process
1. Audit Current State
- List all dependencies
- Check current versions
- Identify outdated packages
- Find security vulnerabilities
2. Analyze Updates
- Check changelogs for breaking changes
- Review version jumps (major, minor, patch)
- Identify dependency conflicts
- Check compatibility requirements
3. Plan Updates
- Prioritize security fixes
- Group related updates
- Order by risk level
- Plan rollback strategy
4. Execute Updates
- Update in small batches
- Run tests after each batch
- Verify functionality
- Document changes
Version Analysis
Semantic Versioning
- Major (X.0.0): Breaking changes, careful review needed
- Minor (0.X.0): New features, backward compatible
- Patch (0.0.X): Bug fixes, safe to update
Update Priority
- Critical: Security vulnerabilities (CVEs)
- High: Deprecated features in use
- Medium: Major version updates
- Low: Minor/patch updates
Common Issues
Breaking Changes
- API signature changes
- Removed features
- Changed defaults
- New peer dependencies
Compatibility
- Node/Python version requirements
- Peer dependency conflicts
- Transitive dependency issues
- Platform-specific problems
Commands by Package Manager
npm/pnpm/yarn
npm outdated # Check outdated
npm audit # Security audit
npm update # Update within range
npm install pkg@latest # Update to latest
Python (pip/poetry)
pip list --outdated # Check outdated
pip-audit # Security audit
poetry update # Update deps
Output Format
Update Report
| Package | Current | Latest | Type | Risk |
|---|---|---|---|---|
| react | 17.0.2 | 18.2.0 | major | medium |
| lodash | 4.17.20 | 4.17.21 | patch | low |
Recommended Actions
- Security fixes (immediate)
- Safe updates (patch versions)
- Feature updates (minor versions)
- Major upgrades (with testing plan)
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.
- 4d ago First seen · 94 lines · 24 tokens per session scan A 4614e1be11cc
dependency-updater is an agent published in the GitHub repository ruchernchong/claude-kit (0 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 546 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-09-01.
Other agents, from other repositories
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.