deps

deps is a skill for Claude Code from drn/dots. It costs 28 tokens per session (1,116 once invoked), scanned A, original, MIT.

A dependency audit and upgrade workflow for software projects. Dependencies are external packages a project relies on, and the workflow checks whether they are outdated or have known security problems.

In plain words
What is it for?
Auditing packages, finding vulnerabilities, upgrading selected or all dependencies, and verifying the result with tests.
Why use it?
It reduces the manual work and risk involved in deciding which packages to update, while checking whether updates break tests.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Auditing packages, finding vulnerabilities, upgrading selected or all dependencies, and verifying the result with tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drn/dots/deps
View source ↗ drn/dots
Install

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.

Any agent
npx skills add drn/dots --skill deps
Clone the repo
git clone --depth 1 https://github.com/drn/dots

Made for: Claude Code.

Wrote 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.

agentmods badge for deps

README.md
[![agentmods](https://agentmods.dev/badge/skills/drn/dots/deps/github.svg)](https://agentmods.dev/skills/drn/dots/deps)
Your own site
<a href="https://agentmods.dev/skills/drn/dots/deps"><img src="https://agentmods.dev/badge/skills/drn/dots/deps/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for deps

Your own site · 80×15
<a href="https://agentmods.dev/skills/drn/dots/deps"><img src="https://agentmods.dev/badge/skills/drn/dots/deps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.01116
Opus 5.5 $0.00011 $0.00446
Sonnet 5.5 $0.00006 $0.00223
Haiku 4.5 $0.00003 $0.00112

Measured 1mo ago against content hash e179094601c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deps 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 1mo 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.

agents/skills/deps/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Audit & Upgrade

Audit outdated dependencies, check for known vulnerabilities, and upgrade with automatic test verification. Rolls back any upgrade that breaks tests.

Arguments

  • $ARGUMENTS - Optional: audit (check only, no changes), upgrade (apply upgrades), or a specific package name to focus on

Context

  • Project type: !find . -maxdepth 1 \( -name go.mod -o -name Gemfile -o -name package.json -o -name Cargo.toml -o -name pyproject.toml \) 2>/dev/null | head -5
  • Lockfiles: !find . -maxdepth 1 \( -name go.sum -o -name Gemfile.lock -o -name package-lock.json -o -name yarn.lock -o -name pnpm-lock.yaml -o -name Cargo.lock -o -name poetry.lock -o -name uv.lock \) 2>/dev/null | head -5

Instructions

Step 1: Detect package manager

Based on the context above, identify the package manager:

File Package Manager Outdated Command
go.mod Go modules go list -m -u all
Gemfile Bundler bundle outdated
package.json npm/yarn/pnpm npm outdated or yarn outdated
Cargo.toml Cargo cargo outdated (if installed)
pyproject.toml pip/poetry/uv pip list --outdated or poetry show --outdated

IF no recognized package manager is found, report "No supported package manager detected." and stop.

IF multiple are found, process each in order.

Step 2: Audit outdated dependencies

Run the appropriate outdated command. Parse the output into a table:

| Package | Current | Latest | Type |
|---------|---------|--------|------|
| foo | 1.2.3 | 2.0.0 | Major |
| bar | 1.0.0 | 1.1.0 | Minor |
| baz | 1.0.0 | 1.0.1 | Patch |

Classify each as Major, Minor, or Patch based on semver difference.

Step 3: Check for vulnerabilities

Run the appropriate audit command:

Package Manager Audit Command
Go govulncheck ./... (if installed, otherwise skip)
Bundler bundle audit check (if installed, otherwise skip)
npm npm audit
Cargo cargo audit (if installed, otherwise skip)
pip pip-audit (if installed, otherwise skip)

Read the full file on GitHub · 125 lines

Changes

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.

  1. 1mo ago First seen · 125 lines · 28 tokens per session scan A e179094601c5

Subscribe to this mod's changes

deps is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 1,116 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens