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 SocketDev/sauce --skill socket-dep-cleanupgit clone --depth 1 https://github.com/SocketDev/sauceWrote 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/socketdev/sauce/socket-dep-cleanup)<a href="https://agentmods.dev/skills/socketdev/sauce/socket-dep-cleanup"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-dep-cleanup/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/socketdev/sauce/socket-dep-cleanup"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-dep-cleanup.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.00051 | $0.02531 |
| Opus 5.5 | $0.00020 | $0.01012 |
| Sonnet 5.5 | $0.00010 | $0.00506 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
socket-dep-cleanup 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dep Cleanup
Evaluate and remove a single unused dependency from your project. This skill targets ONE specific package at a time - searching the entire codebase for all usages, reporting findings, and performing full removal with build and test verification.
When to Use
- The user wants to check if a specific dependency is still used
- The user wants to remove a package they suspect is unused
- The user is cleaning up after removing a feature or refactoring
- The user wants to reduce install size by trimming a specific unnecessary package
- The user asks whether a particular dependency is actually referenced anywhere
Step 1: Identify the Target Package
If the user specifies a package name, use that. Otherwise, ask which package they want to evaluate.
If the user isn't sure which package to evaluate, help them pick one:
- Check
devDependenciesfirst - removing unused dev dependencies is lower risk - Look for packages with names that suggest narrow or outdated functionality
- Suggest running
/socket-scanfirst to get an overview of the dependency landscape
One package at a time. If the user wants to evaluate multiple packages, run this workflow once per package sequentially.
Step 2: Detect the Ecosystem
Identify which ecosystem the target package belongs to by checking manifest and lock files:
| Ecosystem | Manifest Files |
|---|---|
| npm | package.json + package-lock.json |
| pnpm | package.json + pnpm-lock.yaml |
| yarn | package.json + yarn.lock |
| PyPI | requirements.txt, pyproject.toml, setup.py, setup.cfg, Pipfile |
| Cargo | Cargo.toml |
| Bundler | Gemfile |
| Maven | pom.xml |
| NuGet | *.csproj, packages.config |
| Go | go.mod |
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 · 195 lines · 51 tokens per session scan A 157b3bf4aa90
socket-dep-cleanup is a skill published in the GitHub repository SocketDev/sauce (3 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 2,531 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.