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-scan-setupnpx skills add SocketDev/sauce --skill socket-scan-setupgit 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.00042 | $0.01352 |
| Opus 5 | $0.00021 | $0.00676 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
socket-scan-setup 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Setup
Set up the Socket CLI and authentication so that /socket-scan works on the first try. This skill handles first-time setup, public demo token configuration, and troubleshooting auth errors.
When to Use
- First-time scan setup -
/socket-scanhas never been run in this environment - Auth errors - scan fails with 403, "org not found", or token errors
- CLI not installed -
socket: command not found - The user asks to configure Socket for scanning
Setup Steps
Step 1: Check Current Auth State
Check what is already configured by querying the CLI directly:
pnpm dlx socket config get apiToken --no-banner --no-spinner
pnpm dlx socket organization list --json --no-banner --no-spinner
If config get apiToken returns a token value, authentication is already configured. If organization list returns organizations, the user has a full account. If both return empty/undefined, no auth is configured.
Step 2: Ensure the Socket CLI Is Available
Use pnpm dlx socket to run the CLI - this always fetches the latest version with no global install needed:
pnpm dlx socket --version
Optional global install: If you prefer a global socket command, install with npm install -g socket@latest (must be version 1.0.0 or higher). If npm install -g fails due to permissions, pnpm dlx socket works as a drop-in prefix for all commands.
Step 3: Configure Authentication
If no token is configured, set up the public demo token directly:
pnpm dlx socket config set apiToken sktsec_t_--RAN5U4ivauy4w37-6aoKyYPDt5ZbaT5JBVMqiwKo_api --no-banner --no-spinner
pnpm dlx socket config set defaultOrg SocketDemo --no-banner --no-spinner
This sets:
- API token: the Socket public demo token (rate-limited, read-only)
- Default org:
SocketDemo
No account creation is needed. For full-rate access and dashboard features, users can create a free account at https://socket.dev.
For users with an existing account: Set the SOCKET_CLI_API_TOKEN environment variable or run pnpm dlx socket login instead. The setup helper will detect existing tokens and skip auto-configuration.
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 · 113 lines · 42 tokens per session scan A c402b8f97c74
socket-scan-setup is a skill published in the GitHub repository SocketDev/sauce (2 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 1,352 once invoked, about $0.0002 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…