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/laurigates/claude-plugins/code-dep-auditnpx skills add laurigates/claude-plugins --skill code-dep-auditgit clone --depth 1 https://github.com/laurigates/claude-pluginsWrote 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/laurigates/claude-plugins/code-dep-audit)<a href="https://agentmods.dev/skills/laurigates/claude-plugins/code-dep-audit"><img src="https://agentmods.dev/badge/skills/laurigates/claude-plugins/code-dep-audit.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.00035 | $0.00949 |
| Opus 5 | $0.00017 | $0.00475 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
code-dep-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 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/code:dep-audit
Audit project dependencies for vulnerabilities and freshness.
When to Use This Skill
| Use this skill when... | Use something else when... |
|---|---|
| Checking for known CVEs in dependencies | Setting up security scanning CI → /configure:security |
| Preparing a release and need dep health check | Looking for code-level security issues → /code:antipatterns |
| Responding to a vulnerability advisory | Reviewing code quality → /code:review |
| Auditing license compliance | Configuring dependency management → /configure:package-management |
Context
- Package files: !
find . -maxdepth 1 \( -name "package.json" -o -name "package-lock.json" -o -name "yarn.lock" -o -name "bun.lock" -o -name "bun.lockb" -o -name "pyproject.toml" -o -name "requirements.txt" -o -name "Cargo.toml" -o -name "Cargo.lock" -o -name "go.mod" -o -name "go.sum" \) -type f
Parameters
--type: Audit type —security(default),outdated,licenses, orall--fix: Automatically apply safe updates for vulnerable packages
Execution
Execute this dependency audit workflow:
Step 1: Gather audit data
Run the extracted audit script — it detects the package ecosystem, dispatches the matching audit tool, and parses severity / outdated / license-denylist counts into a structured rollup:
bash "${CLAUDE_SKILL_DIR}/scripts/code-dep-audit.sh" --home-dir "$HOME" --project-dir "$(pwd)"
Parse STATUS= and ISSUES: from the output. The script emits ECOSYSTEM=, AUDIT_TOOL=, VULN_CRITICAL/HIGH/MEDIUM/LOW, OUTDATED_COUNT=, LICENSE_ISSUES=, and an ISSUES: block flagging GPL/AGPL licenses (problematic in proprietary projects). When AUDIT_TOOL_AVAILABLE=false, the ecosystem's audit tool is missing — run it via the command in AUDIT_TOOL= if installed, otherwise suggest /configure:security.
Step 2: Apply fixes (if --fix)
For security vulnerabilities:
- Run
npm audit fix/cargo update/pip install --upgradefor safe updates - Report which vulnerabilities were fixed and which require manual intervention
- Run project tests to verify nothing broke
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.
- today First seen · 93 lines · 35 tokens per session scan A 8abfc4301a9b
code-dep-audit is a skill published in the GitHub repository laurigates/claude-plugins (57 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 949 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-09-03.
Other skills, from other repositories
eu-ai-act
Reference knowledge on the EU AI Act (Regulation (EU) 2024/1689): risk tiers, obligations, compliance deadlines including the 2026 AI Omnibus changes, penalties, and scope. Activate when the user asks about the EU AI Act, AI regulation in Europe, high-risk AI compliance, AI transparency or watermarking obligations…
accessibility
Web accessibility patterns and WCAG 2.1/2.2 compliance for inclusive user interfaces. Use when the user asks to build accessible components, audit a UI for a11y issues, fix screen reader problems, implement keyboard navigation, check color contrast ratios, add ARIA attributes, create accessible forms, or establish…
solid
SOLID principles for object-oriented design with multi-language examples (PHP, Java, Python, TypeScript, C++). Use when the user asks to review SOLID compliance, fix a SOLID violation, evaluate class design, reduce coupling, improve extensibility, or apply Single Responsibility, Open/Closed, Liskov Substitution…
subagent-driven-development
Execute a multi-task implementation plan by dispatching one fresh subagent per task with isolated context, then applying a two-stage review (spec compliance and code quality) before advancing. Use when you have a written plan with 3+ tasks, when tasks would otherwise cause context bleed, when you need reproducible…
frontend-dev
Agent team role for UI implementation and frontend architecture. Use when the user asks to build UI components, implement responsive layouts, manage client-side state, integrate with backend APIs, ensure accessibility compliance, or write frontend tests. Owns the user-facing interface — translates design specs into…
governance
Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's…