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 ersinkoc/security-check --skill sc-dependency-auditgit clone --depth 1 https://github.com/ersinkoc/security-checkWrote 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/ersinkoc/security-check/sc-dependency-audit)<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-dependency-audit"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-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.00016 | $0.01975 |
| Opus 5 | $0.00008 | $0.00988 |
| Sonnet 5 | $0.00003 | $0.00395 |
| Haiku 4.5 | $0.00002 | $0.00198 |
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 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.
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 How it starts
The opening of the file, as written. The whole thing — 212 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.
- 7d ago First seen · 212 lines · 16 tokens per session scan A f2fca5bb5798
sc-dependency-audit is a skill published in the GitHub repository ersinkoc/security-check (56 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,975 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…