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 agentmods add skills/viknesh20-20/claude-code-tool-kit/dependency-auditnpx skills add viknesh20-20/claude-code-tool-kit --skill dependency-auditgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/dependency-audit)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/dependency-audit"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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 | $0.00036 | $0.00915 |
| Opus 5 | $0.00018 | $0.00458 |
| Sonnet 5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 4d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Detect Package Manager
!ls package.json package-lock.json yarn.lock pnpm-lock.yaml bun.lockb 2>/dev/null
!ls requirements.txt Pipfile Pipfile.lock pyproject.toml poetry.lock 2>/dev/null
!ls go.mod go.sum 2>/dev/null
!ls Cargo.toml Cargo.lock 2>/dev/null
!ls Gemfile Gemfile.lock 2>/dev/null
!ls *.csproj *.sln 2>/dev/null
!ls composer.json composer.lock 2>/dev/null
!ls mix.exs mix.lock 2>/dev/null
Audit Checks
1. Security Vulnerabilities
Run the appropriate audit command:
| Ecosystem | Command |
|---|---|
| npm | npm audit --json |
| yarn | yarn audit --json |
| pnpm | pnpm audit --json |
| pip | pip audit 2>/dev/null || pip-audit 2>/dev/null |
| Go | govulncheck ./... 2>/dev/null |
| Rust | cargo audit 2>/dev/null |
| Ruby | bundle audit check 2>/dev/null |
| .NET | dotnet list package --vulnerable 2>/dev/null |
| PHP | composer audit 2>/dev/null |
For each vulnerability found:
- Package name and version
- CVE ID or advisory ID
- Severity (Critical/High/Medium/Low)
- Fixed version (if available)
- Whether it's a direct or transitive dependency
2. Outdated Dependencies
Run the appropriate command:
| Ecosystem | Command |
|---|---|
| npm | npm outdated --json |
| pip | pip list --outdated 2>/dev/null |
| Go | go list -m -u all 2>/dev/null |
| Rust | cargo outdated 2>/dev/null |
| Ruby | bundle outdated 2>/dev/null |
Classify updates:
- Patch (1.0.0 → 1.0.1): Usually safe, bug fixes
- Minor (1.0.0 → 1.1.0): New features, backward compatible
- Major (1.0.0 → 2.0.0): Breaking changes, needs review
3. Unused Dependencies
Look for dependencies that are imported in package manifest but never referenced in code:
- Read the dependency list from the manifest
- For each dependency, search the codebase for imports/requires
- Flag any dependency with zero references as potentially unused
Note: Some dependencies are used via CLI, plugins, or config — verify before removing.
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.
- 4d ago First seen · 104 lines · 36 tokens per session scan A 55312961de78
dependency-audit is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 915 once invoked, about $0.0002 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
review-specific-pr
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
security-vulnerability-report
Scan GitHub repositories for security vulnerabilities including Dependabot alerts, code scanning results, and secret scanning findings. Use when auditing repository security, preparing compliance reports, or triaging vulnerability alerts.
afrexai-compliance-engine
Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.
clause
Reviewing legal documents for Terms of Service, Privacy Policy, and Tokushoho compliance. Detects clause gaps and flags risks. Not a substitute for legal advice — consult a lawyer.
oath
Auditing regulatory compliance (SOC2/PCI-DSS/HIPAA/ISO 27001): maps requirements, checks controls, designs audit trails, implements Policy as Code. Use when compliance auditing is needed.
trawl
Architecting crawl and scraping systems: distributed crawler topology, URL frontier, politeness, compliance. Architecture-only. Not for single-page scraping (Vector) or ETL pipelines (Stream).