windsurf-security-basics
Instructions for excluding sensitive files from AI indexing and maintaining a secure local development environment.
Install
mkdir -p .claude/skills/windsurf-security-basics && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4834" && unzip -o skill.zip -d .claude/skills/windsurf-security-basics && rm skill.zipInstalls to .claude/skills/windsurf-security-basics
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Apply Windsurf security best practices for workspace isolation, dataKey capabilities
- →Exclude sensitive files from AI indexing
- →Disable telemetry for privacy compliance
- →Configure AI autocomplete exclusions for secret-containing file types
- →Create security-focused .windsurfrules
- →Audit AI workspace access for potential secret exposure
How it works
The skill uses `.codeiumignore` to exclude files, modifies Windsurf settings to disable telemetry and autocomplete for certain file types, and suggests security rules in `.windsurfrules`.
Inputs & outputs
When to use windsurf-security-basics
- →Protect credentials from AI leakage
- →Configure .codeiumignore for projects
- →Audit AI workspace access
- →Implement least-privilege for AI tools
About this skill
Windsurf Security Basics
Overview
Security best practices for Windsurf AI IDE: controlling what code Cascade can see, preventing secrets from leaking into AI context, managing telemetry, and configuring workspace isolation for regulated environments.
Prerequisites
- Windsurf installed
- Understanding of Codeium's data processing model
- Repository with identified sensitive files
Instructions
Step 1: Exclude Secrets from AI Indexing
Create .codeiumignore at project root (gitignore syntax):
# .codeiumignore — files Codeium/Windsurf will NEVER index or read
# Secrets and credentials
.env
.env.*
.env.local
credentials.json
serviceAccountKey.json
*.pem
*.key
*.p12
*.pfx
# Cloud provider configs
.aws/
.gcloud/
.azure/
# Infrastructure secrets
terraform.tfstate
terraform.tfstate.backup
*.tfvars
vault-config.*
# Customer data
data/customers/
exports/
backups/
*.sql.gz
Default exclusions (automatic): Files in .gitignore, node_modules/, hidden directories (. prefix).
Enterprise: Place a global .codeiumignore at ~/.codeium/ for org-wide exclusions.
Step 2: Disable Telemetry (If Required)
// Windsurf Settings (settings.json)
{
"codeium.enableTelemetry": false,
"codeium.enableSnippetTelemetry": false,
"telemetry.telemetryLevel": "off"
}
Step 3: Configure AI Autocomplete Exclusions
Disable Supercomplete for file types that commonly contain secrets:
{
"codeium.autocomplete.languages": {
"plaintext": false,
"env": false,
"dotenv": false,
"properties": false,
"ini": false
}
}
Step 4: Create Security-Focused .windsurfrules
<!-- .windsurfrules - security section -->
## Security Requirements
- Never suggest hardcoded secrets, API keys, or passwords in code
- Always use environment variables via process.env for secrets
- Never log PII (email, phone, SSN, credit card numbers)
- Use parameterized queries for all database operations
- Never suggest wildcard CORS origins in production code
- All user input must be validated before processing
- Use constant-time comparison for secret/token validation
Step 5: Audit AI Workspace Access
#!/bin/bash
set -euo pipefail
echo "=== Windsurf Security Audit ==="
# Check if .codeiumignore exists
if [ ! -f .codeiumignore ]; then
echo "WARNING: No .codeiumignore — AI can index all non-gitignored files"
fi
# Check for secrets that AI could index
echo "--- Potentially exposed secret files ---"
find . -type f \
-not -path '*/node_modules/*' \
-not -path '*/.git/*' \
\( -name '*.env*' -o -name '*.key' -o -name '*.pem' \
-o -name 'credentials*' -o -name '*secret*' \
-o -name '*.tfvars' -o -name 'serviceAccount*' \) \
2>/dev/null | head -20
# Check if found files are in .codeiumignore
echo "--- Verify all above files are excluded ---"
Step 6: Windsurf Data Processing Model
# What Windsurf/Codeium processes:
data_processing:
indexed_locally:
- File contents for Supercomplete context
- Codebase structure for Cascade awareness
stored: "Local machine only (not sent to cloud for indexing)"
sent_to_cloud:
- Cascade prompts (for AI model inference)
- Code snippets around cursor (for Supercomplete)
stored: "Zero-data retention for paid plans"
never_processed:
- Files in .codeiumignore
- Files in .gitignore (by default)
- Files in node_modules/
compliance:
- SOC 2 Type II certified
- FedRAMP High accredited
- HIPAA BAA available (Enterprise)
- Zero-data retention on paid plans
Security Checklist
-
.codeiumignoreexists with secret file patterns -
.envfiles excluded from AI indexing -
.windsurfrulesincludes security coding standards - Telemetry disabled (if required by policy)
- Autocomplete disabled for secret-containing file types
- No competing AI extensions installed (data exposure risk)
- Team members trained on "never paste secrets into Cascade chat"
- Enterprise: SSO configured, personal accounts blocked
Error Handling
| Security Issue | Detection | Mitigation |
|---|---|---|
| Secret in Cascade suggestion | Appears in AI output | Add source file to .codeiumignore, rotate secret |
| AI indexing .env files | Check .codeiumignore | Add .env* pattern |
| Telemetry sending code | Policy audit | Disable all telemetry settings |
| Dev pastes secret in chat | Cannot detect after the fact | Training + enterprise data retention = 0 |
Examples
Enterprise .codeiumignore
# ~/.codeium/.codeiumignore (global, all workspaces)
*.pem
*.key
*.p12
*.env*
**/secrets/**
**/credentials/**
terraform.tfstate*
*.tfvars
Quick Privacy Check
# Verify critical files are excluded
echo ".env" | while read f; do
[ -f "$f" ] && grep -q "\.env" .codeiumignore 2>/dev/null && echo "$f: PROTECTED" || echo "$f: EXPOSED"
done
Resources
Next Steps
For production deployment, see windsurf-prod-checklist.
Prerequisites
Limitations
- →Secrets appearing in AI output if source file is not in `.codeiumignore`
- →AI indexing .env files if `.env*` pattern is not added to `.codeiumignore`
- →Telemetry sending code if all telemetry settings are not disabled
How it compares
This skill provides a structured approach to securing Windsurf AI environments against data leakage and privacy violations, which differs from a default setup that might expose sensitive information to AI indexing or telemetry.
Compared to similar skills
windsurf-security-basics side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| windsurf-security-basics (this skill) | 1 | 25d | Review | Beginner |
| reverse-engineering-tools | 73 | 3mo | No flags | Advanced |
| game-hacking-techniques | 42 | 2mo | No flags | Advanced |
| solidity-security | 15 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
reverse-engineering-tools
gmh5225
Guide for reverse engineering tools and techniques used in game security research. Use this skill when working with debuggers, disassemblers, memory analysis tools, binary analysis, or decompilers for game security research.
game-hacking-techniques
gmh5225
Guide for game hacking techniques and cheat development. Use this skill when researching memory manipulation, code injection, ESP/aimbot development, overlay rendering, or game exploitation methodologies.
solidity-security
wshobson
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
1password
openclaw
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
senior-security
davila7
Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture, conducting penetration tests, implementing cryptography, or performing security audits.
ghidra
mitsuhiko
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.