dependency-management

dependency-management is a skill for Claude Code from richfrem/agent-plugins-skills. It costs 114 tokens per session (1,675 once invoked), scanned A, original, MIT.

A workflow for managing Python packages and isolated environments across multiple services or a monorepo. It uses separate dependency files for shared components and individual services.

In plain words
What is it for?
Use it when adding, upgrading, or removing Python packages, responding to CVE or GHSA alerts, creating services, or maintaining tiered requirements files.
Why use it?
It prevents unrelated services from sharing an unclear dependency set and gives each service a reproducible package lockfile. It also provides a process for package upgrades and vulnerability alerts.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the dependency-management plugin — 1 skill shipped together

Good fit Use it when adding, upgrading, or removing Python packages, responding to CVE or GHSA alerts, creating services, or maintaining tiered requirements files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/richfrem/agent-plugins-skills/dependency-management
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 richfrem/agent-plugins-skills --skill dependency-management
Clone the repo
git clone --depth 1 https://github.com/richfrem/agent-plugins-skills

Made for: Claude Code.

Or install dependency-management, the plugin that ships this one along with the rest of its 1 skill.

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 dependency-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/dependency-management.svg)](https://agentmods.dev/skills/richfrem/agent-plugins-skills/dependency-management)
Your own site
<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/dependency-management"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/dependency-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,675 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.00114 $0.01675
Opus 5 $0.00057 $0.00838
Sonnet 5 $0.00023 $0.00335
Haiku 4.5 $0.00011 $0.00168

Measured 4d ago against content hash 8f1c0f47ccf7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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

plugins/dependency-management/skills/dependency-management/SKILL.md · 191 lines

How it starts

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

Dependencies

This skill requires Python 3.8+ and standard library only. No external packages needed.

To install this skill's dependencies:

pip-compile ./requirements.in
pip install -r ./requirements.txt

See ./requirements.txt for the dependency lockfile (currently empty — standard library only).


Dependency Management

  1. One runtime per service. Each isolated service owns its own ./requirements.txt lockfile.

Script Architecture & Packaging

For plugin packaging, DRY script distribution, and Windows symlink/junction compatibility rules, see the authoritative shared plugin packaging guidelines.

Repository Layout (Example)

src/
├── requirements-core.in          # Tier 1: shared baseline (fastapi, pydantic…)
├── requirements-core.txt         # Lockfile for core
├── services/
│   ├── auth_service/
│   │   ├── requirements.in       # Tier 2: inherits core + auth deps
│   │   └── requirements.txt
│   ├── payments_service/
│   │   ├── requirements.in
│   │   └── requirements.txt
│   └── database_service/
│       ├── requirements.in
│       └── requirements.txt

Tiered Hierarchy

Tier Scope File Examples
1 – Core Shared by >80% of services requirements-core.in fastapi, pydantic, httpx
2 – Specialized Service-specific heavyweights <service>/requirements.in stripe, redis, asyncpg
3 – Dev tools Never in production containers requirements-dev.in pytest, black, ruff

Each service .in file usually begins with -r ../../requirements-core.in to inherit the core dependencies.

Workflow: Adding or Upgrading a Package

  1. Declare — Add or update the version constraint in the correct .in file.

    • If the package is needed by most services → requirements-core.in
    • If only one service → that service's .in
    • Security floor pins use >= syntax: cryptography>=46.0.5
  2. Lock — Compile the lockfile:

    # Core
    pip-compile src/requirements-core.in \
      --output-file src/requirements-core.txt
    
    # Individual service (example: auth)
    pip-compile src/services/auth_service/requirements.in \
      --output-file src/services/auth_service/requirements.txt
    

    Because services inherit core via -r, recompiling a service also picks up core changes.

Read the full file on GitHub · 191 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. 4d ago First seen · 191 lines · 114 tokens per session scan A 8f1c0f47ccf7

Subscribe to this mod's changes

dependency-management is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 1,675 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-09-03.

Related

Other skills, from other repositories

kapso-whatsapp

How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…

desplega-ai/agent-swarm · 156 tokens

fastify-best-practices

This skill should be used when working on any Fastify project or when the user asks about Fastify best practices, conventions, or patterns. Trigger when: working on a Fastify project, creating Fastify plugins, registering routes, using decorators, organizing Fastify application structure, using @fastify/autoload…

RadOrigin-LLC/RAD-Claude-Skills · 110 tokens

fastify-hooks-lifecycle

This skill should be used when implementing Fastify hooks, understanding hook execution order, using onRequest/preParsing/preValidation/preHandler/preSerialization/onError/onSend/onResponse hooks, using onReady/onListen/onClose/onRoute/onRegister application hooks, debugging hook chain issues, adding authentication…

RadOrigin-LLC/RAD-Claude-Skills · 85 tokens

fastify-production

This skill should be used when deploying Fastify to production, configuring Fastify security headers, setting up reverse proxy with Fastify, implementing graceful shutdown, configuring @fastify/helmet, @fastify/cors, @fastify/rate-limit, trustProxy settings, Kubernetes Fastify deployment, Fastify performance tuning…

RadOrigin-LLC/RAD-Claude-Skills · 97 tokens

fastify-troubleshooting

This skill should be used when debugging Fastify issues, identifying Fastify anti-patterns, diagnosing common Fastify mistakes, performing Fastify error troubleshooting, investigating request.body undefined in hook, fixing decorator shared across requests, resolving hook executing twice, handling reply already sent…

RadOrigin-LLC/RAD-Claude-Skills · 103 tokens

fastify-schemas-validation

This skill should be used when writing Fastify JSON schemas, configuring Ajv validation, using fast-json-stringify serialization, defining request body/querystring/params/headers schemas, sharing schemas with addSchema and $ref, using fluent-json-schema, configuring response schemas, handling validation errors…

RadOrigin-LLC/RAD-Claude-Skills · 87 tokens