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 snyk/studio-recipes --skill snyk-fixgit clone --depth 1 https://github.com/snyk/studio-recipesWrote 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/snyk/studio-recipes/snyk-fix)<a href="https://agentmods.dev/skills/snyk/studio-recipes/snyk-fix"><img src="https://agentmods.dev/badge/skills/snyk/studio-recipes/snyk-fix/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/snyk/studio-recipes/snyk-fix"><img src="https://agentmods.dev/badge/skills/snyk/studio-recipes/snyk-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00143 | $0.06543 |
| Opus 5 | $0.00072 | $0.03272 |
| Sonnet 5 | $0.00029 | $0.01309 |
| Haiku 4.5 | $0.00014 | $0.00654 |
Grade A, and why
snyk-fix 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 11d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snyk Fix (All-in-One)
Complete security remediation workflow: Parse → Scan → Analyze → Fix → Validate → Summary → (Optional) PR
Modes:
- Single Mode (default): Fix one vulnerability type at a time (all instances in same file)
- Batch Mode: Fix multiple vulnerabilities in priority order (triggered by "all", "batch", severity filter, or count)
Phase 1: Input Parsing
Parse user input to extract:
- mode: Single (default) or Batch
- scan_type:
code,sca, orboth(inferred from context) - target_vulnerability: Specific issue ID, CVE, package name, file, or vuln type
- target_path: File or directory (defaults to project root)
- severity_filter / max_fixes: For batch mode (default max: 20)
Mode & Scan Type Detection
| Signal | Mode | Scan Type |
|---|---|---|
| "all", severity filter, count ("top 5"), or "batch" | Batch | both |
| Specific vuln ID, single type, file reference, or no batch indicators | Single (default) | — |
| Explicit "code"/"sast"/"static" | — | code |
| Explicit "sca"/"dependency"/"package"/package manager name | — | sca |
SNYK- or CVE- ID provided |
— | both |
| Vulnerability type (XSS, SQL injection, path traversal, etc.) or file reference | — | code |
| Package name reference | — | sca |
| No hints | — | both (highest priority issue) |
Phase 1B: Batch Mode Planning (Skip if Single Mode)
- Run both
mcp_snyk_snyk_code_scanandmcp_snyk_snyk_sca_scanon project root. - Filter by user-specified severity, type, path, or count.
- Group by vulnerability type (same ID + file for code; same package for SCA). Sort Critical → High → Medium → Low; within same priority, prefer issues with available fixes.
- Display fix plan as a numbered table (index, type, severity, target, instance count) with estimated file/package changes. Wait for user confirmation before proceeding.
- If user says "adjust": allow plan modification.
- Execute fixes in order (Phase 3 or 4 per item → Phase 5 validate → track result). On failure: stop if
stop_on_failure=true, else continue. - Proceed to Phase 6B after all attempts.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 556 lines · 143 tokens per session scan A 012bfa1bcb58
snyk-fix is a skill published in the GitHub repository snyk/studio-recipes (62 stars, last pushed 7d ago), licensed Apache-2.0. It adds 143 tokens to every session and 6,543 once invoked, about $0.0007 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…