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 ao92265/claude-code-playbook --skill dependency-auditgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/dependency-audit)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/dependency-audit"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/dependency-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.1 | $0.00079 | $0.00383 |
| Opus 5 | $0.00039 | $0.00192 |
| Sonnet 5 | $0.00016 | $0.00077 |
| Haiku 4.5 | $0.00008 | $0.00038 |
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 7d 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.
What it actually says
Run a comprehensive dependency audit for the current project.
Steps
- Run
scripts/audit.sh <project-directory>to generate a structured report- Example:
scripts/audit.sh /path/to/your/project - If no directory is given, it defaults to the current working directory
- The script covers: package.json check, security audit, outdated packages, unused dependency detection, and lock file health
- It will NOT run
npm install,npm audit fix, or modify any files
- Example:
Output Format
Security Summary
| Severity | Count |
|---|---|
| Critical | N |
| High | N |
| ... | ... |
Top issues: (list)
Outdated Packages
- Major updates available: (list)
- Minor/patch updates: (count)
Potentially Unused Dependencies
- (list or "None detected")
Recommendations
Prioritized list of actions to take.
Important
- Do NOT run
npm installor modify any files - Do NOT run
npm audit fix— report only - If a command fails, note it and continue with other checks
- Keep the report concise and actionable
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.
- 7d ago First seen · 52 lines · 79 tokens per session scan A 790dbcbdba9e
dependency-audit is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 20d ago), licensed MIT. It adds 79 tokens to every session and 383 once invoked, about $0.0004 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…