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 fatihkan/badi --skill sc-dependency-auditgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/sc-dependency-audit)<a href="https://agentmods.dev/skills/fatihkan/badi/sc-dependency-audit"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/sc-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/fatihkan/badi/sc-dependency-audit"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/sc-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.00016 | $0.01968 |
| Opus 5 | $0.00008 | $0.00984 |
| Sonnet 5 | $0.00003 | $0.00394 |
| Haiku 4.5 | $0.00002 | $0.00197 |
Grade A, and why
sc-dependency-audit scanned grade A with 2 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 2d 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Gradle/Maven plugins that execute arbitrary code Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `setup.py` with `os.system()`, `subprocess`, or network calls This is a copy
92% identical to sc-dependency-audit — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC: Dependency Audit — Supply Chain & Dependency Security
Purpose
Analyzes all project dependencies for known vulnerabilities, supply chain risks, typosquatting attempts, and dangerous build-time behaviors. Covers all major package ecosystems: npm, PyPI, crates.io, Maven Central, NuGet, Packagist, and Go modules.
Activation
Runs as part of Phase 1 (Reconnaissance), immediately after sc-recon.
Output
File: security-report/dependency-audit.md
Phase 1: Discovery
Lock File Detection
Search for dependency manifest and lock files:
| Ecosystem | Manifest | Lock File |
|---|---|---|
| Node.js | package.json |
package-lock.json, yarn.lock, pnpm-lock.yaml |
| Python | requirements.txt, pyproject.toml, Pipfile, setup.py, setup.cfg |
Pipfile.lock, poetry.lock |
| Go | go.mod |
go.sum |
| Rust | Cargo.toml |
Cargo.lock |
| Java | pom.xml, build.gradle, build.gradle.kts |
gradle.lockfile |
| C# | *.csproj, packages.config |
packages.lock.json |
| PHP | composer.json |
composer.lock |
| Ruby | Gemfile |
Gemfile.lock |
Dependency Inventory
For each detected ecosystem:
- Parse manifest files to list all direct dependencies with version constraints
- Parse lock files to list all transitive dependencies with resolved versions
- Count total dependencies (direct + transitive)
- Flag missing lock files — if manifest exists but no lock file, flag as risk
Known Vulnerability Scanning
For each dependency, check for known vulnerabilities by analyzing:
- Version age — flag dependencies not updated in 2+ years
- Known CVE patterns — check version ranges against known vulnerable version ranges
- Deprecated packages — check for deprecation notices in manifest metadata
- Yanked/retracted versions — detect usage of versions pulled from registries
Common vulnerable dependency patterns to flag:
Node.js:
lodash< 4.17.21 (prototype pollution)minimist< 1.2.6 (prototype pollution)json5< 2.2.2 (prototype pollution)node-fetch< 2.6.7 (SSRF via redirect)express< 4.19.2 (open redirect)jsonwebtoken< 9.0.0 (algorithm confusion)- Any dependency using
evalorFunction()in source
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.
- 2d ago First seen · 211 lines · 16 tokens per session scan A 54968f10af78
sc-dependency-audit is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,968 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 2 findings (unrestricted tool access, runs shell commands). It is 92% identical to sc-dependency-audit, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.