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.
git 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/commands/snyk/studio-recipes/snyk-fix)<a href="https://agentmods.dev/commands/snyk/studio-recipes/snyk-fix"><img src="https://agentmods.dev/badge/commands/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/commands/snyk/studio-recipes/snyk-fix"><img src="https://agentmods.dev/badge/commands/snyk/studio-recipes/snyk-fix.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.00020 | $0.07382 |
| Opus 5 | $0.00010 | $0.03691 |
| Sonnet 5 | $0.00004 | $0.01476 |
| Haiku 4.5 | $0.00002 | $0.00738 |
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 9d 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 — 768 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snyk Fix (All-in-One)
Overview
Complete security remediation workflow in a single command. Scans for vulnerabilities, fixes them, validates the fix, and optionally creates a PR.
Workflow: Parse → Scan → Analyze → Fix → Validate → Summary → (Optional) PR
Example Usage
| Command | Behavior |
|---|---|
/snyk-fix |
Auto-detect scan type, fix highest priority issue (all instances) |
/snyk-fix code |
SAST scan only, fix highest priority code issue (all instances in file) |
/snyk-fix sca |
SCA scan only, fix highest priority dependency issue |
/snyk-fix SNYK-JS-LODASH-1018905 |
Fix specific Snyk issue by ID |
/snyk-fix CVE-2021-44228 |
Find and fix specific CVE |
/snyk-fix lodash |
Fix highest priority issue in lodash package |
/snyk-fix server.ts |
Code scan on file, fix highest priority issue (all instances) |
/snyk-fix sca express |
Fix highest priority issue in express package |
/snyk-fix XSS |
Fix all XSS vulnerabilities in highest priority file |
/snyk-fix path traversal |
Fix all path traversal vulnerabilities |
Phase 1: Input Parsing
Parse user input to extract:
- scan_type: Explicit (
code,sca,both) or infer from context - target_vulnerability: Specific issue ID, CVE, package name, file reference, or vulnerability type
- target_path: File or directory to focus on (defaults to project root)
Scan Type Detection Rules (in priority order)
- Explicit code: User says "code", "sast", "static" → Code scan
- Explicit sca: User says "sca", "dependency", "package", "npm", "pip", "maven" → SCA scan
- Vulnerability ID provided:
- Starts with
SNYK-→ run both scans to locate it - Contains
CVE-→ run both scans to find it
- Starts with
- Vulnerability type provided: User mentions type like "XSS", "SQL injection", "path traversal" → Code scan
- File reference: User mentions
.ts,.js,.py, etc. file → Code scan on that file - Package reference: User mentions known package name (e.g., "lodash", "express") → SCA scan
- Default (no hints): Run BOTH scans, select highest priority issue
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.
- 9d ago First seen · 768 lines · 20 tokens per session scan A ec5e75af7574
snyk-fix is a command published in the GitHub repository snyk/studio-recipes (62 stars, last pushed 6d ago), licensed Apache-2.0. It adds 20 tokens to every session and 7,382 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.