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/jayrha/agentskills/dependency-upgradernpx skills add JayRHa/AgentSkills --skill dependency-upgradergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWhat 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.00115 | $0.01936 |
| Opus 5 | $0.00057 | $0.00968 |
| Sonnet 5 | $0.00023 | $0.00387 |
| Haiku 4.5 | $0.00012 | $0.00194 |
Grade A, and why
dependency-upgrader 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Upgrader
Overview
This skill drives safe, auditable dependency upgrades across ecosystems (npm/yarn/pnpm, pip/poetry/uv, cargo, go modules, bundler, maven/gradle, composer). The core discipline: one upgrade per commit, tests green between each, and a known-good rollback point at all times. Never bulk-upgrade everything and hope.
Keywords: dependency upgrade, bump packages, outdated, semver, breaking change, changelog, migration guide, lockfile, CVE, security advisory, Dependabot, Renovate, rollback, npm audit, pip-audit.
Use this skill when the user wants to update libraries, patch a vulnerability, migrate a major version, or vet an automated bump PR.
Core Principles
- Isolate. One package (or one tightly-coupled group) per commit. A failed upgrade must be revertable without touching unrelated work.
- Read before you write. Always inspect the changelog / release notes / migration guide before bumping across a major version.
- Tiered risk. Patch < minor < major. Batch low-risk; isolate high-risk.
- Test gate. The test suite (or a defined verification command) must pass before each commit. No green, no commit.
- Always have a rollback. Know the exact git SHA and lockfile state to
return to. See
references/rollback.md.
Workflow
Follow these steps in order. Do not skip the inventory or the changelog read.
1. Establish a clean baseline
- Confirm the working tree is clean (
git status). If not, stop and ask the user how to proceed — never upgrade on top of uncommitted changes. - Record the current commit SHA as the rollback anchor.
- Run the test suite once to confirm it is green before you start. If tests are already failing, report that and stop — you cannot attribute later failures otherwise.
- Identify the ecosystem and the verification command. See
references/ecosystems.mdfor the canonical commands per package manager.
2. Inventory outdated dependencies
- Run the detector script:
python3 scripts/check_outdated.py --dir <repo>. It auto-detects the ecosystem and prints a risk-tiered table (patch / minor / major) plus any known advisories it can surface from the native auditor. - Or run the native tool directly (
npm outdated,pip list --outdated,cargo outdated,go list -m -u all) — seereferences/ecosystems.md. - Classify each candidate by semver jump and by whether it is a direct or transitive dependency.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 159 lines · 115 tokens per session scan A c66e101b2905
dependency-upgrader is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,936 once invoked, about $0.0006 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
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
interpreting-mod-author-instructions
Use when deciding how to correctly download/install a Bethesda mod per the author's instructions — triggers "how do I install", "FOMOD choices", "which file to download", "author说明", "install instructions", "which variant", "按作者说明安装", "这个mod怎么装". NOT for deciding whether to include the mod (use evaluating-bgs-mods)…
using-bgs-archive
Use when the user wants to inspect, list, extract, unpack, or repack Bethesda BA2/BSA archives; determine archive format/version/compression; or build archive assets for an MO2 overlay. Triggers - "unpack BA2", "extract BSA", "pack archive", "inspect archive", "bgs-archive".
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
design-director
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.