dependency-policy

dependency-policy is a skill for Claude Code, Codex from vmobifystudio/app-dev-team. It costs 25 tokens per session (329 once invoked), scanned A, original, MIT.

Audit declared dependencies, lockfiles, tool versions, compatibility, licenses, and upgrade evidence before implementation or release.

Skill for Claude CodeCodex

Installs and runs on its own, but its text points at files inside the plugin that ships it — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed.

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.

agentmods
npx agentmods add skills/vmobifystudio/app-dev-team/dependency-policy
Any agent
npx skills add vmobifystudio/app-dev-team --skill dependency-policy
Clone the repo
git clone --depth 1 https://github.com/vmobifystudio/app-dev-team

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/dependency-policy.svg)](https://agentmods.dev/skills/vmobifystudio/app-dev-team/dependency-policy)
Your own site
<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/dependency-policy"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/dependency-policy.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 329 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00025 $0.00329
Opus 5 $0.00013 $0.00164
Sonnet 5 $0.00005 $0.00066
Haiku 4.5 $0.00003 $0.00033

Measured today against content hash e61336cce3a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dependency-policy 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 today.

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.

skills/dependency-policy/SKILL.md · 30 lines

What it actually says

Dependency policy

Use when a project adds, removes, upgrades, or relies on a package, SDK, compiler, runtime, service, model, or third-party API. Also use during onboarding, architecture review, and release preparation.

Procedure

  1. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/dependency-check.mjs" <project-root>.
  2. Read the architecture and stack-defaults documents before choosing a version.
  3. Confirm the declaration and lockfile changed together where the ecosystem uses a lockfile.
  4. Record direct dependency, purpose, version constraint, transitive risk, license, minimum platform, deprecation status, and rollback/removal plan in the ticket evidence.
  5. Use the project-pinned toolchain (gradlew, Package.resolved, lockfile, or equivalent). Never silently install a global version to make a check pass.
  6. If a dependency is unapproved, unpinned, unlocked, incompatible, or unknown, block or escalate; do not “resolve” it by picking the newest version from memory.

Policy

  • Prefer platform-native libraries and the smallest dependency surface.
  • A new dependency needs a written reason and an owner.
  • A version claim must name its source and date; “latest” is not evidence.
  • A failed or unavailable vulnerability/license lookup is CANNOT EVALUATE, not a clean result.
  • Never update a lockfile without reviewing the resulting transitive diff.
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. today First seen · 30 lines · 25 tokens per session scan A e61336cce3a5

Subscribe to this mod's changes

dependency-policy is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 25 tokens to every session and 329 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-03.

Related

Other skills, from other repositories

execute-task

Implement one task (or a cohesion bundle) from a signed-off spec (Ready or Active): recompute the execution freshness gate, write the verifying test first, implement to green, run the project's full CI with adaptive retry, converge via the configured reviewsequence (default /polish --nested), then open a draft PR…

inkatze/planwright · 111 tokens

builder

Detect a project's stack and recommend or apply the universal mechanical quality guards from planwright's core catalog (formatter, linters, type-checker, test runner, secret scan, commit hooks, CI gate), plus the growable breadth dimensions. Escalates stake-bearing decisions (auth, data modeling, security posture…

inkatze/planwright · 100 tokens

spec-walkthrough

Render a spec bundle (or a chosen slice) into a plain-language, didactic comprehension artifact a human reads and judges for themselves: an unaided cold read before kickoff, re-orientation mid-execution, or onboarding to a finished or abandoned spec. Standalone and strictly read-only: it renders any status, never…

inkatze/planwright · 100 tokens

drain

Run the on-demand drain pass over every spec bundle's Gate deferral entries: evaluate structured GATE(when:) conditions, surface date and free-text gates, report malformed ones, inventory each live bundle's [manual] test-spec entries, and surface the observations log's unmined state. Read-only; nothing is…

inkatze/planwright · 75 tokens

orchestrate

Advance one planwright spec by one step: pick the next ready unit critical-path-first (or a cohesion bundle), run the freshness gate, record the dispatch under the per-spec lock, and dispatch /execute-task via the backend. A stateless, disposable control tower; a reconcile sweep rebuilds from disk. Never merges, marks…

inkatze/planwright · 101 tokens

spec-kickoff

Walk a spec bundle section by section to mutual understanding, producing the signed-off kickoff brief downstream skills execute from. On sign-off: runs the Discovery-Rigor lens pass, flips Draft to Ready, records the sign-off record (anchor last), commits, pushes, opens a draft PR, then on clean completion marks the…

inkatze/planwright · 108 tokens