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/codebygarv/ai-skills/dependency-auditornpx skills add codebygarv/Ai-skills --skill dependency-auditorgit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/dependency-auditor)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/dependency-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/dependency-auditor.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00524 |
| Opus 5 | $0.00020 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
dependency-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Review a project's dependency manifest for bloat, risk, and duplication — packages that shouldn't be there, packages that duplicate functionality, and packages that carry maintenance or licensing risk.
When to Use
- The dependency list has grown over time without anyone auditing it.
- Before adding a new dependency, to check if an existing one already covers the need.
- Investigating bundle size or install time bloat.
What to Analyze
- Unnecessary packages — dependencies for functionality that's a few lines of code, or that duplicate a built-in language/runtime feature.
- Duplication — multiple packages solving the same problem (e.g. two date libraries, two HTTP clients) introduced at different times by different people.
- Maintenance risk — packages that are unmaintained (no updates in years, open critical issues with no response), single-maintainer with no succession, or deprecated in favor of a successor.
- Bundle/install cost — a heavy dependency pulled in for a small fraction of its functionality (check if a lighter alternative or a direct implementation would do).
- Version drift — dependencies significantly behind current major versions, especially where the gap blocks picking up security fixes.
- License risk — copyleft licenses (e.g. GPL) in a codebase that otherwise ships under a permissive/proprietary license, where that's likely unintentional.
Output Format
- Grouped: Remove/replace candidates (unnecessary or duplicated) → Risk (unmaintained, license, badly behind on versions) → Note (heavier than needed but not urgent).
- Each entry: package name, the concern, and the concrete recommendation (remove, replace with X, upgrade to version Y, or just flag for awareness).
- State clearly when a recommendation needs verification (e.g. "confirm no other code path relies on this package's transitive behavior before removing").
Avoid
- Recommending removal of a dependency without checking whether it's actually used across the codebase, not just imported once.
- Treating every slightly-outdated version as urgent — distinguish "years behind with known CVEs" from "one minor version behind."
- Making licensing calls as if they're legal advice — flag for review, don't declare a license is definitely a problem without appropriate caveats.
What ships with it
2 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.
- 4d ago First seen · 36 lines · 40 tokens per session scan A 804bdb6fe640
dependency-auditor is a skill published in the GitHub repository codebygarv/Ai-skills (24 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 524 once invoked, about $0.0002 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
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis for Redis/Valkey, Bun.Archive for tarballs, Bun.Image image processing, Bun.WebView…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…