/dependency-audit
Use when running ecosystem-specific vulnerability scans across project dependencies (npm/composer/pip/cargo/go/etc), with optional auto-fix.
$ npx -y skills add fusengine/agents --skill dependency-audit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/dependency-audit
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when running ecosystem-specific vulnerability scans across project dependencies (npm/composer/pip/cargo/go/etc), with optional auto-fix.
SKILL.md
dependency-audit.SKILL.mdname: dependency-audit
description: "Use when running ecosystem-specific vulnerability scans across project dependencies (npm/composer/pip/cargo/go/etc), with optional auto-fix."
argument-hint: "[--fix] [ecosystem]"
user-invocable: true
<objective> This skill runs native package-manager audit tools across a project's full dependency tree, detecting the package manager from lock files and running the matching command: npm/yarn/pnpm/bun audit, composer audit, pip-audit/safety check, cargo audit, govulncheck, pod audit, or bundle audit.
It parses each tool's output, classifies findings by severity (CRITICAL/HIGH/MEDIUM/LOW), and suggests fix versions or alternatives. With the --fix flag it applies safe auto-fixes where supported (npm audit fix, cargo audit fix) and gives manual guidance for ecosystems without auto-fix.
Out of scope: researching a single named dependency's CVE history in depth belongs to cve-research. </objective>
Dependency Audit Skill
Overview
Run dependency vulnerability checks using native package manager audit tools.
Supported Ecosystems
| Ecosystem | Tool | Auto-fix | |-----------|------|----------| | npm/yarn/pnpm/bun | `npm audit` / `yarn audit` | Yes | | PHP/Composer | `composer audit` | Manual | | Python/pip | `pip-audit` / `safety check` | Manual | | Rust/Cargo | `cargo audit` | Yes | | Go | `govulncheck ./...` | Manual | | Swift/CocoaPods | `pod audit` | Manual | | Ruby/Bundler | `bundle audit` | Manual |
Workflow
1. **Detect** package manager from lock files 2. **Run** appropriate audit command 3. **Parse** output for vulnerabilities 4. **Classify** by severity (CRITICAL/HIGH/MEDIUM/LOW) 5. **Suggest** fix versions or alternatives
Auto-Fix Support
When `--fix` flag is used:
- `npm audit fix` for safe updates
- `cargo audit fix` for Rust
- Manual guidance for other ecosystems
References
- [Audit Commands](references/audit-commands.md)
- [Report Template](references/templates/audit-report.md)
Read more
name: dependency-audit description: "Use when running ecosystem-specific vulnerability scans across project dependencies (npm/composer/pip/cargo/go/etc), with optional auto-fix." argument-hint: "[--fix] [ecosystem]" user-invocable: true
<objective> This skill runs native package-manager audit tools across a project's full dependency tree, detecting the package manager from lock files and running the matching command: npm/yarn/pnpm/bun audit, composer audit, pip-audit/safety check, cargo audit, govulncheck, pod audit, or bundle audit.
It parses each tool's output, classifies findings by severity (CRITICAL/HIGH/MEDIUM/LOW), and suggests fix versions or alternatives. With the --fix flag it applies safe auto-fixes where supported (npm audit fix, cargo audit fix) and gives manual guidance for ecosystems without auto-fix.
Out of scope: researching a single named dependency's CVE history in depth belongs to cve-research. </objective>
Dependency Audit Skill
Overview
Run dependency vulnerability checks using native package manager audit tools.
Supported Ecosystems
| Ecosystem | Tool | Auto-fix | |-----------|------|----------| | npm/yarn/pnpm/bun | `npm audit` / `yarn audit` | Yes | | PHP/Composer | `composer audit` | Manual | | Python/pip | `pip-audit` / `safety check` | Manual | | Rust/Cargo | `cargo audit` | Yes | | Go | `govulncheck ./...` | Manual | | Swift/CocoaPods | `pod audit` | Manual | | Ruby/Bundler | `bundle audit` | Manual |
Workflow
1. **Detect** package manager from lock files 2. **Run** appropriate audit command 3. **Parse** output for vulnerabilities 4. **Classify** by severity (CRITICAL/HIGH/MEDIUM/LOW) 5. **Suggest** fix versions or alternatives
Auto-Fix Support
When `--fix` flag is used:
- `npm audit fix` for safe updates
- `cargo audit fix` for Rust
- Manual guidance for other ecosystems
References
- [Audit Commands](references/audit-commands.md)
- [Report Template](references/templates/audit-report.md)
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

