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 hamzaPixl/pixl-ai --skill dependency-reviewgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/dependency-review)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/dependency-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/dependency-review/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/hamzapixl/pixl-ai/dependency-review"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/dependency-review.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.01011 |
| Opus 5 | $0.00029 | $0.00505 |
| Sonnet 5 | $0.00012 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
dependency-review 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Dependency review pipeline: discovery → vulnerability scan → outdated check → license audit → unused detection → report. Read-only analysis that produces an actionable report.
Required References
Before starting, read references/standards/security-audit.md for CVE severity classification and dependency risk assessment patterns.
Step 1: Discovery
- Package manager detection:
package.json+package-lock.json→ npmpackage.json+yarn.lock→ yarnpackage.json+pnpm-lock.yaml→ pnpmpackage.json+bun.lockb→ bunpyproject.tomlorrequirements.txt→ pip/poetrygo.mod→ Go modules
- Dependency inventory:
- Count production vs dev dependencies
- Identify monorepo structure (workspaces)
- Check for multiple lockfiles (inconsistency risk)
Step 2: Vulnerability Scan
Run the appropriate audit command:
# npm
npm audit --json 2>/dev/null || true
# yarn
yarn audit --json 2>/dev/null || true
# pnpm
pnpm audit --json 2>/dev/null || true
# pip
pip audit --format json 2>/dev/null || true
# or if pip-audit not available:
# Check against GitHub Advisory Database via grep
Parse results and categorize:
- Critical: Remote code execution, SQL injection, auth bypass
- High: XSS, SSRF, path traversal
- Medium: DoS, information disclosure
- Low: Minor issues, theoretical attacks
Step 3: Outdated Check
# npm
npm outdated --json 2>/dev/null || true
# pip
pip list --outdated --format json 2>/dev/null || true
Categorize updates:
- Major (breaking): Requires migration work
- Minor (feature): Safe to update, review changelog
- Patch (fix): Safe to update immediately
Flag dependencies more than 2 major versions behind.
Step 4: License Audit
- Check licenses of all production dependencies:
# npm — check package.json of each dep npx license-checker --json 2>/dev/null || true - Flag problematic licenses:
- GPL/AGPL in a commercial project (copyleft risk)
- UNLICENSED or missing license
- Custom/proprietary licenses
- Check for license compatibility with project license
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.
- 12d ago First seen · 138 lines · 58 tokens per session scan A 0d48edb423d1
dependency-review is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 1,011 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…