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-scan-setupgit 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-scan-setup)<a href="https://agentmods.dev/skills/socketdev/sauce/socket-scan-setup"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-scan-setup/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-scan-setup"><img src="https://agentmods.dev/badge/skills/socketdev/sauce/socket-scan-setup.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.00039 | $0.00784 |
| Opus 5.5 | $0.00016 | $0.00314 |
| Sonnet 5.5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
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 6d 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 — 76 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, user-owned authentication, 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 account access without printing credential values:
pnpm dlx socket organization list --json --no-banner --no-spinner
A successful result with a non-demo organization confirms account access. An empty result, demo-only result, or error leaves authentication unverified. Do not run config get apiToken; it prints the credential.
Step 2: Ensure the Socket CLI Is Available
Use pnpm dlx socket to run the CLI. It fetches the latest version without a global install:
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 the user has no account credential, ask whether they want to create an account or log in. If they decline, leave authentication unconfigured. Do not write an API token or default organization.
For users with an existing account: Set the SOCKET_CLI_API_TOKEN environment variable or run pnpm dlx socket login.
Step 4: Verify Setup
Run the account check from Step 1. Treat an empty result, demo-only result, or error as unverified authentication. Do not print a token to confirm setup.
Step 5: Test a Scan
Run a test scan only after the account check returns a non-demo organization:
pnpm dlx socket scan create . --tmp --json --no-banner --no-spinner
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.
- 6d ago Changed · -37 lines · -3 tokens per session 980732a9055b
- 1mo ago First seen · 113 lines · 42 tokens per session scan A c402b8f97c74
socket-scan-setup is a skill published in the GitHub repository SocketDev/sauce (3 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 784 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
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…