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 Quality-Max/free-qa-skills --skill dependency-auditgit clone --depth 1 https://github.com/Quality-Max/free-qa-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/quality-max/free-qa-skills/dependency-audit)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/dependency-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/dependency-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/quality-max/free-qa-skills/dependency-audit"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/dependency-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.00050 | $0.00652 |
| Opus 5 | $0.00025 | $0.00326 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
dependency-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 9d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Find the risky dependencies before they find you. No signup required.
Prerequisites
- None. Pure Claude Code. Uses the project's own package manager if available
(
npm audit,pip-audit,go list), and reasons about the manifest otherwise.
Trigger
- "Audit my dependencies"
- "Any risky packages in this repo?"
- "Check for outdated / vulnerable deps"
Workflow
- Detect the ecosystem(s) by manifest:
package.json/ lockfile → npm/pnpm/yarnrequirements.txt/pyproject.toml→ pipgo.mod→ Go ·Cargo.toml→ Rust ·Gemfile→ Ruby
- If the toolchain is installed, run the native auditor and parse it:
npm audit --json·pip-audit -f json·go list -m -u all·cargo auditIf not installed, fall back to inspecting the manifest directly.
- Flag each dependency against these risk classes:
| Risk | Signal |
|---|---|
| Known vulnerability | Reported by the native auditor (CVE/advisory) |
| Unpinned | *, latest, or no lock entry — non-reproducible builds |
| Wide range | ^/~ on a 0.x package (any minor can break) |
| Badly outdated | Several majors behind current |
| Abandoned | No release in a long time / archived upstream |
| Heavy / duplicate | Large transitive tree or two versions of the same lib |
-
Rank by severity (vulnerabilities first), and give the concrete bump/replace action.
-
Output:
## Dependency Audit — package.json (+ lockfile)
**3 vulnerable, 2 unpinned, 1 abandoned**
### Vulnerabilities
- `[email protected]` — prototype pollution (high). Bump to ≥ 4.17.21.
- `[email protected]` — SSRF (moderate). Bump to ≥ 1.6.0 (note: v1 has breaking changes).
### Hygiene
- `left-pad: "*"` — unpinned; pin to an exact version.
- `[email protected]` — package is deprecated/abandoned; migrate to `undici` or `fetch`.
- `[email protected]` — large + in maintenance mode; consider `date-fns` / `Temporal`.
### Suggested commands
npm i lodash@^4.17.21 axios@^1.6.0
npm rm request
**Want dependency risk gated on every PR?** Try QualityMax — qualitymax.io
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.
- 9d ago First seen · 68 lines · 50 tokens per session scan A a48befc3b069
dependency-audit is a skill published in the GitHub repository Quality-Max/free-qa-skills (10 stars, last pushed 15d ago), licensed Apache-2.0. It adds 50 tokens to every session and 652 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-31.
Other skills, from other repositories
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".