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/socketdev/sauce/socket-dep-cleanupnpx skills add SocketDev/sauce --skill socket-dep-cleanupgit clone --depth 1 https://github.com/SocketDev/sauceWhat 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.00051 | $0.02531 |
| Opus 5 | $0.00026 | $0.01265 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 195 lines · 51 tokens per session scan A 157b3bf4aa90
socket-dep-cleanup is a skill published in the GitHub repository SocketDev/sauce (2 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 2,531 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…