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 Claude-Code-Community-Ireland/claude-code-resources --skill dependency-auditgit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/claude-code-community-ireland/claude-code-resources/dependency-audit)<a href="https://agentmods.dev/skills/claude-code-community-ireland/claude-code-resources/dependency-audit"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/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/claude-code-community-ireland/claude-code-resources/dependency-audit"><img src="https://agentmods.dev/badge/skills/claude-code-community-ireland/claude-code-resources/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.00031 | $0.03202 |
| Opus 5.5 | $0.00012 | $0.01281 |
| Sonnet 5.5 | $0.00006 | $0.00640 |
| Haiku 4.5 | $0.00003 | $0.00320 |
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 1mo 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Evaluating New Dependencies
Before adding any dependency, run through this evaluation checklist. Every "no" answer is a risk that must be explicitly accepted.
Evaluation Checklist
- Maintenance: Last commit within 6 months? Issues responded to? More than one maintainer?
- Adoption: More than 1,000 weekly downloads (npm) or equivalent? Used by known projects?
- Bundle size: Checked via bundlephobia.com or equivalent? Is tree-shaking supported?
- License: Compatible with your project license? (See license matrix below)
- Security: No open CVEs? Has a security policy? Publishes signed releases?
- API surface: Does it do one thing well, or is it a kitchen-sink package?
- Alternatives: Have you checked if the standard library or an existing dep covers this?
- Transitive deps: How many transitive dependencies does it pull in?
Quick Evaluation Commands
# npm — check package info
npm info <package> --json | jq '{name, version, license, homepage, maintainers}'
# Check download stats
npm info <package> --json | jq '.downloads'
# Bundle size (requires bundlephobia API or website)
# Visit: https://bundlephobia.com/package/<package>
# Check for known vulnerabilities before installing
npm audit --dry-run --package-lock-only
# Python — check package metadata
pip show <package>
pip index versions <package>
# Rust — check crate info
cargo info <crate>
Decision Framework
| Factor | Accept | Investigate | Reject |
|---|---|---|---|
| Weekly downloads | > 50,000 | 1,000 - 50,000 | < 1,000 |
| Last commit | < 3 months | 3 - 12 months | > 12 months |
| Open issues | < 50 with triage | 50 - 200 | > 200 untriaged |
| Maintainers | >= 2 | 1 active | 0 active |
| Transitive deps | < 5 | 5 - 20 | > 20 |
| Bundle size (JS) | < 10 KB gzipped | 10 - 50 KB | > 50 KB (for a single feature) |
| License | MIT, Apache-2.0, BSD | ISC, MPL-2.0 | GPL, AGPL, SSPL, unlicensed |
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.
- 1mo ago First seen · 450 lines · 31 tokens per session scan A 6a4bc21a7713
dependency-audit is a skill published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 3,202 once invoked, about $0.0001 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…