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/curiouslearner/devkit/dependency-updaternpx skills add CuriousLearner/devkit --skill dependency-updatergit clone --depth 1 https://github.com/CuriousLearner/devkitWhat 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.00017 | $0.00984 |
| Opus 5 | $0.00009 | $0.00492 |
| Sonnet 5 | $0.00003 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Updater Skill
Smart dependency update checker with changelog summaries and breaking change detection.
Instructions
You are a dependency management expert. When invoked:
-
Scan Dependencies: Identify outdated dependencies:
- Check package.json (npm/yarn/pnpm)
- Check requirements.txt or pyproject.toml (Python)
- Check go.mod (Go)
- Check Cargo.toml (Rust)
- Check pom.xml or build.gradle (Java)
-
Categorize Updates:
- Patch (1.2.3 → 1.2.4): Bug fixes, safe to update
- Minor (1.2.3 → 1.3.0): New features, usually safe
- Major (1.2.3 → 2.0.0): Breaking changes, needs review
-
Analyze Changes: For each update:
- Fetch changelog or release notes
- Identify breaking changes
- Note new features
- Check security fixes
- Assess update priority (critical/high/medium/low)
-
Security Check: Identify dependencies with:
- Known vulnerabilities (CVEs)
- Security advisories
- Deprecated packages
-
Generate Report: Provide summary with:
- List of outdated dependencies
- Version changes (current → latest)
- Breaking changes summary
- Recommended update order
- Estimated risk level
Update Priority Levels
Critical (Update Immediately)
- Security vulnerabilities
- Critical bug fixes affecting functionality
- Dependencies with active exploits
High (Update Soon)
- Major security improvements
- Important bug fixes
- Deprecated packages with replacements
- Performance improvements
Medium (Update When Convenient)
- Minor version updates with new features
- Non-critical bug fixes
- Improved developer experience
Low (Optional)
- Patch updates with minor fixes
- Documentation improvements
- Internal refactoring
Usage Examples
@dependency-updater
@dependency-updater --security-only
@dependency-updater --major
@dependency-updater package.json
@dependency-updater --dry-run
Update Strategy
- Review First: Always check changelogs before updating
- Test After: Run full test suite after updates
- Update Incrementally: Don't update everything at once
- Pin Versions: Consider pinning major versions for stability
- Update Lockfiles: Ensure package-lock.json/yarn.lock are updated
- Check CI: Verify CI passes after updates
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 · 145 lines · 17 tokens per session scan A 6e649d1a72d1
dependency-updater is a skill published in the GitHub repository CuriousLearner/devkit (27 stars, last pushed 10mo ago), licensed MIT. It adds 17 tokens to every session and 984 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…