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 skills add kazdenc/builder-skills --skill deps-auditgit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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.
[](https://agentmods.dev/skills/kazdenc/builder-skills/deps-audit)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/deps-audit"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/deps-audit/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.
<a href="https://agentmods.dev/skills/kazdenc/builder-skills/deps-audit"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/deps-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00058 | $0.01666 |
| Opus 5 | $0.00029 | $0.00833 |
| Sonnet 5 | $0.00012 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
deps-audit 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 10d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit project dependencies and produce a categorized report with a prioritized upgrade plan. Surface vulnerabilities, unused packages, and bundle bloat.
Step 1: Read Package Manifest
Read package.json (or the specified manifest file). Catalog:
- All
dependenciesand their pinned/range versions - All
devDependenciesand their pinned/range versions - Any
peerDependenciesoroptionalDependencies - Package manager in use (npm, pnpm, yarn) from lock file presence
- Node/runtime engine constraints if declared
Step 2: Check for Vulnerabilities
Run the appropriate audit command for the detected package manager:
| Package Manager | Command | Notes |
|---|---|---|
| npm | npm audit --json |
Parse JSON output for severity counts |
| pnpm | pnpm audit --json |
Similar JSON structure |
| yarn (v1) | yarn audit --json |
NDJSON output, parse line by line |
| yarn (berry) | yarn npm audit --json |
Different output format |
For each vulnerability found, capture:
- Package name and installed version
- Severity (critical, high, moderate, low)
- CVE identifier if available
- Fix available (yes/no) and which version resolves it
- Whether it is a direct or transitive dependency
Step 3: Identify Outdated Packages
Run npm outdated --json (or equivalent) and group results:
| Update Type | Risk Level | Action |
|---|---|---|
| Patch (1.2.3 → 1.2.4) | Low | Safe to update; bug fixes only |
| Minor (1.2.3 → 1.3.0) | Low–Medium | Usually safe; new features, no breaking changes |
| Major (1.2.3 → 2.0.0) | Medium–High | Breaking changes expected; read changelog first |
| Deprecated | High | Package abandoned; find replacement |
Flag packages more than 2 major versions behind as high priority.
Step 4: Find Unused Dependencies
Scan the codebase for actual import/require usage of each declared dependency:
- Search for
import ... from '<package>'andrequire('<package>')patterns - Check framework config files that reference packages implicitly (Babel, PostCSS, ESLint, Tailwind plugins)
- Check scripts in
package.jsonthat invoke CLI tools - Check for
@types/*packages whose corresponding runtime package is used
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.
- 10d ago First seen · 160 lines · 58 tokens per session scan A 8689f82a2e8f
deps-audit is a skill published in the GitHub repository kazdenc/builder-skills (45 stars, last pushed 6mo ago), licensed MIT. It adds 58 tokens to every session and 1,666 once invoked, about $0.0003 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
commercial-opportunity-review
Review Product, offering, catalog, quote, and sale evidence for commercial opportunities.
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.
outcome-review
Review whether a funded product bet changed its intended outcome and append evidence-backed learning.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
roadmap-refresh
Refresh Now, Next, and Later from funded demand, objectives, dependencies, and delivery evidence.