Secure At Inception
Proactively scan all newly generated or modified code to prevent security vulnerabilities before they enter the codebase. Provides intelligent scanning decisions, caching, and filtering to focus only on NEW issues.
File Type → Scan Type Reference
| Scan Type |
Trigger Files |
MCP Tool |
| SAST (Code) |
Source files: .js, .ts, .py, .java, .go, .rb, .php, .cs, .swift, .kt, .scala, .rs, .c, .cpp, .dart, and more |
snyk_code_scan |
| SCA (Dependencies) |
Manifests: package.json, requirements.txt, pom.xml, build.gradle, Gemfile, go.mod, Cargo.toml, *.csproj, composer.json, and more |
snyk_sca_scan |
| IaC |
Infrastructure: .tf, .tfvars, K8s YAML (with apiVersion/kind), template.json/.yaml, ARM JSON, serverless.yml |
snyk_iac_scan |
Skip: binary files, non-IaC JSON/YAML, documentation (.md, .txt, .rst), assets, test fixtures.
Phase 1: Change Detection
Step 1.1: Gather Changed Files
Check for changes using one of these methods (in order of preference):
- Git diff (if in a git repo):
git diff --name-only HEAD
git diff --name-only --cached # staged files
git status --porcelain
- Session context: Track files created/modified during the current session
- User-specified path: If user provides a specific file or directory
Step 1.2: Categorize Files by Scan Type
Use the File Type → Scan Type Reference table above to map each changed file to the appropriate scan. IaC YAML is distinguished from generic YAML by the presence of apiVersion/kind (Kubernetes) or AWSTemplateFormatVersion (CloudFormation).
Phase 2: Execute Scans
Run SAST, SCA, and IaC scans in parallel — they are independent of each other. Use the parameters below for each applicable scan type (determined by the File Type → Scan Type Reference table).
Step 2.1: SAST Scan (snyk_code_scan)
path: directory containing changed source files (or project root); scan each file individually if < 5 files changed, otherwise scan the parent directory
severity_threshold: "medium" (default) or as configured
Step 2.2: SCA Scan (snyk_sca_scan)
path: project root or directory containing the manifest
all_projects: true (for monorepos)
severity_threshold: "medium" (default) or as configured
- Note: SCA scans the entire dependency tree, not just direct changes.
Step 2.3: IaC Scan (snyk_iac_scan)
path: directory containing IaC files
severity_threshold: "medium" (default) or as configured
Phase 3: Filter to New Issues
Apply these filters before reporting to surface only issues introduced by the current changes.
SAST: Include a finding only if its file+line falls within a modified line range from git diff -U0. Parse @@ -X,Y +A,B @@ hunks to determine changed ranges; exclude findings outside those ranges as pre-existing.
SCA: Include only if a new or updated package now has MORE vulnerabilities or higher severity than before. Apply the Net Improvement Rule — if the change reduces overall vulnerability count or severity, do NOT block.
IaC: Include only if the misconfiguration is in a newly added or modified resource block.
Phase 4: Report & Decision
Step 4.1: Severity Threshold Configuration
| Mode |
Block On |
Warn On |
Allow |
| Strict |
Low+ |
- |
- |
| Standard |
High+ |
Medium |
Low |
| Relaxed |
Critical only |
High |
Medium, Low |
Step 4.2: Generate Report
## Secure At Inception Scan Results
### Summary
| Scan Type | New Issues | Blocked |
|----------------------|------------|---------|
| Code (SAST) | X | Yes/No |
| Dependencies (SCA) | Y | Yes/No |
| Infrastructure (IaC) | Z | Yes/No |
### New Code Vulnerabilities (SAST)
| Severity | Type | File | Line | Description |
|----------|---------------|------------|------|-----------------------|
| High | SQL Injection | src/db.ts | 45 | User input in query |
### New Dependency Vulnerabilities (SCA)
| Severity | Package | Vulnerability | Fix Version |
|----------|------------------|----------------------|-------------|
| Critical | lodash@4.17.15 | Prototype Pollution | 4.17.21 |
### New Infrastructure Issues (IaC)
| Severity | Resource | Issue | Recommendation |
|----------|----------------|-----------------------|--------------------------|
| High | aws_s3_bucket | Public access enabled | Set block_public_access |
### Recommended Actions
1. `/snyk-fix SNYK-JS-LODASH-1234` - Fix lodash vulnerability
2. Review `src/db.ts:45` for SQL injection fix
### Decision: [BLOCKED / ALLOWED]
[Reason based on severity threshold]
Step 4.3: Block Decision Logic
If any NEW issue severity >= threshold:
BLOCKED - do not proceed until fixed
Provide specific fix commands
Else:
ALLOWED - safe to proceed
Note any warnings for future attention
Phase 5: Track Metrics
After each scan that finds and helps fix issues, run snyk_send_feedback with:
path: project root (absolute path)
preventedIssuesCount: count of NEW issues found (delta, not cumulative)
fixedExistingIssuesCount: 0 (this skill prevents, doesn't fix existing issues)
Only count issues found in NEW code that would have been committed without this scan.
Best Practices
Error Handling
| Situation |
Action |
| Authentication error |
Run snyk_auth and retry; prompt user for manual authentication if still failing |
| Scan timeout |
Retry once with smaller scope; report partial results if still failing |
| No changes detected |
Report "No code changes detected - nothing to scan"; offer full project scan on request |
| Unsupported files only |
Report "No scannable files in changes" with a list of skipped file types and reasons |
Constraints
- New Issues Only: Never block on pre-existing issues (that's remediation's job)
- Minimal Noise: Filter aggressively to avoid alert fatigue
- Fast Feedback: Complete scan within 30 seconds for typical changes
- Non-Destructive: Never modify code, only report findings
- Actionable Output: Every finding must have a clear fix path
1---
2name: secure-at-inception
3description: |
4 Proactive security scanning for newly generated or modified code. Intelligently detects changes,
5 runs appropriate scans (SAST, SCA, IaC), filters to only NEW issues, and prevents vulnerabilities
6 at the source. Use this skill when:
7 - Agent generates new code files
8 - Agent modifies existing code
9 - User asks to "scan for security issues" or "check my changes"
10 - Before committing changes
11 - User mentions "secure at inception", "proactive scan", or "security check"
12allowed-tools: "mcp_snyk_snyk_code_scan mcp_snyk_snyk_sca_scan mcp_snyk_snyk_iac_scan mcp_snyk_snyk_send_feedback Read Bash Grep"
13license: Apache-2.0
14compatibility: |
15 Requires Snyk MCP server connection and authenticated Snyk account.
16 Git repository recommended for change detection (git diff).
17 Supports 20+ programming languages for SAST, all major package managers for SCA,
18 and Terraform/Kubernetes/CloudFormation/ARM for IaC scanning.
19metadata:
20 source: https://skillmd.com/skills/snyk/secure-at-inception
21 author: Snyk
22 version: 1.0.0
23---
24
25# Secure At Inception
26
27Proactively scan all newly generated or modified code to prevent security vulnerabilities before they enter the codebase. Provides intelligent scanning decisions, caching, and filtering to focus only on NEW issues.
28
29---
30
31## File Type → Scan Type Reference
32
33| Scan Type | Trigger Files | MCP Tool |
34|-----------|--------------|----------|
35| SAST (Code) | Source files: `.js`, `.ts`, `.py`, `.java`, `.go`, `.rb`, `.php`, `.cs`, `.swift`, `.kt`, `.scala`, `.rs`, `.c`, `.cpp`, `.dart`, and more | `snyk_code_scan` |
36| SCA (Dependencies) | Manifests: `package.json`, `requirements.txt`, `pom.xml`, `build.gradle`, `Gemfile`, `go.mod`, `Cargo.toml`, `*.csproj`, `composer.json`, and more | `snyk_sca_scan` |
37| IaC | Infrastructure: `.tf`, `.tfvars`, K8s YAML (with `apiVersion`/`kind`), `template.json`/`.yaml`, ARM JSON, `serverless.yml` | `snyk_iac_scan` |
38
39**Skip**: binary files, non-IaC JSON/YAML, documentation (`.md`, `.txt`, `.rst`), assets, test fixtures.
40
41---
42
43## Phase 1: Change Detection
44
45### Step 1.1: Gather Changed Files
46
47Check for changes using one of these methods (in order of preference):
48
491. **Git diff** (if in a git repo):
50 ```bash
51 git diff --name-only HEAD
52 git diff --name-only --cached # staged files
53 git status --porcelain
54 ```
552. **Session context**: Track files created/modified during the current session
563. **User-specified path**: If user provides a specific file or directory
57
58### Step 1.2: Categorize Files by Scan Type
59
60Use the File Type → Scan Type Reference table above to map each changed file to the appropriate scan. IaC YAML is distinguished from generic YAML by the presence of `apiVersion`/`kind` (Kubernetes) or `AWSTemplateFormatVersion` (CloudFormation).
61
62---
63
64## Phase 2: Execute Scans
65
66Run SAST, SCA, and IaC scans in **parallel** — they are independent of each other. Use the parameters below for each applicable scan type (determined by the File Type → Scan Type Reference table).
67
68### Step 2.1: SAST Scan (`snyk_code_scan`)
69- `path`: directory containing changed source files (or project root); scan each file individually if < 5 files changed, otherwise scan the parent directory
70- `severity_threshold`: `"medium"` (default) or as configured
71
72### Step 2.2: SCA Scan (`snyk_sca_scan`)
73- `path`: project root or directory containing the manifest
74- `all_projects`: `true` (for monorepos)
75- `severity_threshold`: `"medium"` (default) or as configured
76- Note: SCA scans the entire dependency tree, not just direct changes.
77
78### Step 2.3: IaC Scan (`snyk_iac_scan`)
79- `path`: directory containing IaC files
80- `severity_threshold`: `"medium"` (default) or as configured
81
82---
83
84## Phase 3: Filter to New Issues
85
86Apply these filters before reporting to surface only issues introduced by the current changes.
87
88**SAST**: Include a finding only if its file+line falls within a modified line range from `git diff -U0`. Parse `@@ -X,Y +A,B @@` hunks to determine changed ranges; exclude findings outside those ranges as pre-existing.
89
90**SCA**: Include only if a new or updated package now has MORE vulnerabilities or higher severity than before. Apply the **Net Improvement Rule** — if the change reduces overall vulnerability count or severity, do NOT block.
91
92**IaC**: Include only if the misconfiguration is in a newly added or modified resource block.
93
94---
95
96## Phase 4: Report & Decision
97
98### Step 4.1: Severity Threshold Configuration
99
100| Mode | Block On | Warn On | Allow |
101|------|----------|---------|-------|
102| Strict | Low+ | - | - |
103| Standard | High+ | Medium | Low |
104| Relaxed | Critical only | High | Medium, Low |
105
106### Step 4.2: Generate Report
107
108```
109## Secure At Inception Scan Results
110
111### Summary
112| Scan Type | New Issues | Blocked |
113|----------------------|------------|---------|
114| Code (SAST) | X | Yes/No |
115| Dependencies (SCA) | Y | Yes/No |
116| Infrastructure (IaC) | Z | Yes/No |
117
118### New Code Vulnerabilities (SAST)
119| Severity | Type | File | Line | Description |
120|----------|---------------|------------|------|-----------------------|
121| High | SQL Injection | src/db.ts | 45 | User input in query |
122
123### New Dependency Vulnerabilities (SCA)
124| Severity | Package | Vulnerability | Fix Version |
125|----------|------------------|----------------------|-------------|
126| Critical | lodash@4.17.15 | Prototype Pollution | 4.17.21 |
127
128### New Infrastructure Issues (IaC)
129| Severity | Resource | Issue | Recommendation |
130|----------|----------------|-----------------------|--------------------------|
131| High | aws_s3_bucket | Public access enabled | Set block_public_access |
132
133### Recommended Actions
1341. `/snyk-fix SNYK-JS-LODASH-1234` - Fix lodash vulnerability
1352. Review `src/db.ts:45` for SQL injection fix
136
137### Decision: [BLOCKED / ALLOWED]
138[Reason based on severity threshold]
139```
140
141### Step 4.3: Block Decision Logic
142
143```
144If any NEW issue severity >= threshold:
145 BLOCKED - do not proceed until fixed
146 Provide specific fix commands
147Else:
148 ALLOWED - safe to proceed
149 Note any warnings for future attention
150```
151
152---
153
154## Phase 5: Track Metrics
155
156After each scan that finds and helps fix issues, run `snyk_send_feedback` with:
157- `path`: project root (absolute path)
158- `preventedIssuesCount`: count of NEW issues found (delta, not cumulative)
159- `fixedExistingIssuesCount`: `0` (this skill prevents, doesn't fix existing issues)
160
161Only count issues found in NEW code that would have been committed without this scan.
162
163---
164
165## Best Practices
166
167- **Run automatically** after generating or modifying code, and before suggesting a commit; also on request for explicit security checks.
168- **Cache results** keyed by `file + content_hash` with a 12-hour TTL; only rescan changed files and batch by directory.
169- **False positives**: Use a `.snyk` policy file to suppress confirmed false positives, then re-run to verify:
170 ```yaml
171 ignore:
172 SNYK-JS-EXAMPLE-12345:
173 - '*':
174 reason: 'False positive - input is validated upstream'
175 expires: 2025-12-31
176 ```
177- **Threshold tuning**: Start with Standard mode; switch to Relaxed if blocks are too frequent, or Strict after low/medium severity incidents.
178- **CI/CD integration**: Invoke on pull request creation or pushes to feature branches; block merge if threshold is exceeded.
179
180---
181
182## Error Handling
183
184| Situation | Action |
185|-----------|--------|
186| Authentication error | Run `snyk_auth` and retry; prompt user for manual authentication if still failing |
187| Scan timeout | Retry once with smaller scope; report partial results if still failing |
188| No changes detected | Report "No code changes detected - nothing to scan"; offer full project scan on request |
189| Unsupported files only | Report "No scannable files in changes" with a list of skipped file types and reasons |
190
191---
192
193## Constraints
194
1951. **New Issues Only**: Never block on pre-existing issues (that's remediation's job)
1962. **Minimal Noise**: Filter aggressively to avoid alert fatigue
1973. **Fast Feedback**: Complete scan within 30 seconds for typical changes
1984. **Non-Destructive**: Never modify code, only report findings
1995. **Actionable Output**: Every finding must have a clear fix path