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-patchgit 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-patch)<a href="https://agentmods.dev/skills/socketdev/sauce/socket-dep-patch"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-dep-patch/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-patch"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-dep-patch.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.00042 | $0.03135 |
| Opus 5.5 | $0.00017 | $0.01254 |
| Sonnet 5.5 | $0.00008 | $0.00627 |
| Haiku 4.5 | $0.00004 | $0.00314 |
Grade B, and why
socket-dep-patch scanned grade B 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 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| Standalone (macOS/Linux) | `curl -fsSL https://raw.githubusercontent.com/SocketDev/socket-patch/main/install.sh \| sh` | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Standalone (macOS/Linux) | `curl -fsSL https://raw.githubusercontent.com/SocketDev/socket-patch/main/install.sh \| sh` | How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dep Patch
Apply Socket's binary-level security patches to vulnerable dependencies without changing their version numbers. This skill uses socket-patch apply to fix known vulnerabilities in-place. Patches are applied in bulk - socket-patch apply patches all available packages at once.
After applying patches, this skill checks whether the project is set up to keep patches applied automatically (via postinstall hooks, CI steps, or Dockerfile layers). If not, it walks through configuring automated patching.
How This Differs from /socket-dep-upgrade
/socket-dep-patch (this skill) |
/socket-dep-upgrade |
|
|---|---|---|
| Primary tool | socket-patch apply |
socket fix |
| What it does | Applies binary-level patches without changing versions | Upgrades dependency versions to fix CVEs |
| Version changes? | No | Yes |
| Code changes needed? | No | Possibly (API migration for major bumps) |
| Scope | All patchable packages at once | One dependency at a time |
| When to use | You need fixes without version churn, or the upstream fix doesn't exist yet | You want to bring dependencies up to date |
Use /socket-dep-patch when you want to fix vulnerabilities without risking breaking changes from version upgrades. Use /socket-dep-upgrade when you want full version upgrades with automated code migration.
When to Use
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 · 292 lines · 42 tokens per session scan B 3392712b2fe1
socket-dep-patch is a skill published in the GitHub repository SocketDev/sauce (3 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 3,135 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…