Security Review
SentryOfficialPublished by Sentry
- Skill
- Review and audit
- Security
- CC-BY-SA-4.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Security Review skill provides a structured approach to auditing code for security vulnerabilities. It emphasizes deep research into data flow and context to distinguish between theoretical risks and truly exploitable issues. By focusing on attacker-controlled inputs and framework-specific mitigations, it reduces false positives and ensures that reported findings are actionable and high-confidence.
What it does
- Performs systematic security audits on provided code snippets or files.
- Traces data flow to confirm if inputs are attacker-controlled or server-controlled.
- Evaluates code against common vulnerability patterns like injection, XSS, and authentication flaws.
- Filters out false positives by checking for framework-level protections and sanitization.
- Categorizes findings by severity and confidence levels.
- Provides a standardized reporting format for identified vulnerabilities.
When to use it
- When you need to audit code for potential security vulnerabilities.
- When performing an OWASP-based security review.
- When you need to verify if a specific code pattern is exploitable.
- When checking for common security issues like SQL injection, XSS, or insecure authentication.
Advantages
- Reduces noise by filtering out theoretical issues and server-controlled configurations.
- Ensures high-confidence reporting by requiring codebase research before flagging.
- Provides clear, actionable remediation advice for identified vulnerabilities.
- Standardizes the security review process across different codebases.
Usage examples
- “Perform a security review on this file: [code snippet]”
- The agent will analyze the code, trace the data flow of inputs, and provide a report of any high-confidence vulnerabilities found, or state that none were identified.
- “Check this API endpoint for potential injection vulnerabilities.”
- The agent will examine the endpoint's input handling and database queries to determine if user input is properly parameterized or sanitized.
- “Audit this authentication logic for security issues.”
- The agent will review the authentication implementation against best practices, such as password storage algorithms and brute-force protections.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/getsentry/security-review/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip security-review.zip -d .agents/skills
Documentation by Sentry
<!-- Reference material based on OWASP Cheat Sheet Series (CC BY-SA 4.0) https://cheatsheetseries.owasp.org/ -->
Security Review Skill
Identify exploitable security vulnerabilities in code. Report only HIGH CONFIDENCE findings—clear vulnerable patterns with attacker-controlled input.
Scope: Research vs. Reporting
CRITICAL DISTINCTION:
Report on: Only the specific file, diff, or code provided by the user
Research: The ENTIRE codebase to build confidence before reporting
Before flagging any issue, you MUST research the codebase to understand:
Where does this input actually come from? (Trace data flow)
Is there validation/sanitization elsewhere?
How is this configured? (Check settings, config files, middleware)
What framework protections exist?
Do NOT report issues based solely on pattern matching. Investigate first, then report only what you're confident is exploitable.
Confidence Levels
| Level | Criteria | Action |
|---|---|---|
| HIGH | Vulnerable pattern + attacker-controlled input confirmed | Report with severity |
| MEDIUM | Vulnerable pattern, input source unclear | Note as "Needs verification" |
| LOW | Theoretical, best practice, defense-in-depth | Do not report |
Do Not Flag
General Rules
Test files (unless explicitly reviewing test security)
Dead code, commented code, documentation strings
Patterns using constants or server-controlled configuration
Code paths that require prior authentication to reach (note the auth requirement instead)
Server-Controlled Values (NOT Attacker-Controlled)
These are configured by operators, not controlled by attackers:
| Source | Example | Why It's Safe |
|---|---|---|
| Django settings | settings.API_URL, settings.ALLOWED_HOSTS | Set via config/env at deployment |
| Environment variables | os.environ.get('DATABASE_URL') | Deployment configuration |
| Config files | config.yaml, app.config['KEY'] | Server-side files |
| Framework constants | django.conf.settings.* | Not user-modifiable |
| Hardcoded values | BASE_URL = "https://api.internal" | Compile-time constants |
SSRF Example - NOT a vulnerability:
# SAFE: URL comes from Django settings (server-controlled)
response = requests.get(f"{settings.SEER_AUTOFIX_URL}{path}")SSRF Example - IS a vulnerability:
# VULNERABLE: URL comes from request (attacker-controlled)
response = requests.get(request.GET.get('url'))Framework-Mitigated Patterns
Check language guides before flagging. Common false positives:
| Pattern | Why It's Usually Safe |
|---|---|
Django {{ variable }} | Auto-escaped by default |
React {variable} | Auto-escaped by default |
Vue {{ variable }} | Auto-escaped by default |
User.objects.filter(id=input) | ORM parameterizes queries |
cursor.execute("...%s", (input,)) | Parameterized query |
innerHTML = "<b>Loading...</b>" | Constant string, no user input |
Only flag these when:
Django:
{{ var|safe }},{% autoescape off %},mark_safe(user_input)React:
dangerouslySetInnerHTML={{__html: userInput}}Vue:
v-html="userInput"ORM:
.raw(),.extra(),RawSQL()with string interpolation
Review Process
1. Detect Context
What type of code am I reviewing?
| Code Type | Load These References |
|---|---|
| API endpoints, routes | authorization.md, authentication.md, injection.md |
| Django/DRF views, permission classes, object-level access | Use the django-access-review skill if available for access control; otherwise authorization.md |
| Frontend, templates | xss.md, csrf.md, modern-threats.md (DOM clobbering, prototype pollution) |
| File handling, uploads | file-security.md |
| Crypto, secrets, tokens | cryptography.md, data-protection.md |
| Data serialization | deserialization.md |
| External requests | ssrf.md |
| Business workflows | business-logic.md |
| GraphQL, REST design | api-security.md |
| Config, headers, CORS | misconfiguration.md |
| CI/CD, dependencies | supply-chain.md |
| Error handling | error-handling.md |
| Audit, logging | logging.md |
Object merging/cloning, __proto__, DOM id/name lookups, WebSocket handlers, LLM prompt construction | modern-threats.md |
2. Load Language Guide
Based on file extension or imports:
| Indicators | Guide |
|---|---|
.py, django, flask, fastapi | languages/python.md |
.js, .ts, express, react, vue, next | languages/javascript.md |
For other languages there is no dedicated guide; rely on the references/ files and verify framework protections directly in the codebase.
3. Load Infrastructure Guide (if applicable)
| File Type | Guide |
|---|---|
Dockerfile, .dockerignore | infrastructure/docker.md |
| GitHub Actions workflows | Use the gha-security-review skill if available; otherwise references/supply-chain.md |
| Other CI/CD pipelines, lockfiles, package manifests | references/supply-chain.md |
4. Research Before Flagging
For each potential issue, research the codebase to build confidence:
Where does this value actually come from? Trace the data flow.
Is it configured at deployment (settings, env vars) or from user input?
Is there validation, sanitization, or allowlisting elsewhere?
What framework protections apply?
Only report issues where you have HIGH confidence after understanding the broader context.
5. Verify Exploitability
For each potential finding, confirm:
Is the input attacker-controlled?
| Attacker-Controlled (Investigate) | Server-Controlled (Usually Safe) |
|---|---|
request.GET, request.POST, request.args | settings.X, app.config['X'] |
request.json, request.data, request.body | os.environ.get('X') |
request.headers (most headers) | Hardcoded constants |
request.cookies (unsigned) | Internal service URLs from config |
URL path segments: /users/<id>/ | Database content from admin/system |
| File uploads (content and names) | Signed session data |
| Database content from other users | Framework settings |
| WebSocket messages |
Does the framework mitigate this?
Check language guide for auto-escaping, parameterization
Check for middleware/decorators that sanitize
Is there validation upstream?
Input validation before this code
Sanitization libraries (DOMPurify, bleach, etc.)
6. Report HIGH Confidence Only
Skip theoretical issues. Report only what you've confirmed is exploitable after research.
Severity Classification
| Severity | Impact | Examples |
|---|---|---|
| Critical | Direct exploit, severe impact, no auth required | RCE, SQL injection to data, auth bypass, hardcoded secrets |
| High | Exploitable with conditions, significant impact | Stored XSS, SSRF to metadata, IDOR to sensitive data |
| Medium | Specific conditions required, moderate impact | Reflected XSS, CSRF on state-changing actions, path traversal |
| Low | Defense-in-depth, minimal direct impact | Missing headers, verbose errors, weak algorithms in non-critical context |
Quick Patterns Reference
Always Flag (Critical)
eval(user_input) # Any language
exec(user_input) # Any language
pickle.loads(user_data) # Python
yaml.load(user_data) # Python (not safe_load)
unserialize($user_data) # PHP
deserialize(user_data) # Java ObjectInputStream
shell=True + user_input # Python subprocess
child_process.exec(user) # Node.jsAlways Flag (High)
innerHTML = userInput # DOM XSS
dangerouslySetInnerHTML={user} # React XSS
v-html="userInput" # Vue XSS
f"SELECT * FROM x WHERE {user}" # SQL injection
`SELECT * FROM x WHERE ${user}` # SQL injection
os.system(f"cmd {user_input}") # Command injectionAlways Flag (Secrets)
password = "hardcoded"
api_key = "sk-..."
AWS_SECRET_ACCESS_KEY = "..."
private_key = "-----BEGIN"Check Context First (MUST Investigate Before Flagging)
# SSRF - ONLY if URL is from user input, NOT from settings/config
requests.get(request.GET['url']) # FLAG: User-controlled URL
requests.get(settings.API_URL) # SAFE: Server-controlled config
requests.get(f"{settings.BASE}/{x}") # CHECK: Is 'x' user input?
# Path traversal - ONLY if path is from user input
open(request.GET['file']) # FLAG: User-controlled path
open(settings.LOG_PATH) # SAFE: Server-controlled config
open(f"{BASE_DIR}/{filename}") # CHECK: Is 'filename' user input?
# Open redirect - ONLY if URL is from user input
redirect(request.GET['next']) # FLAG: User-controlled redirect
redirect(settings.LOGIN_URL) # SAFE: Server-controlled config
# Weak crypto - ONLY if used for security purposes
hashlib.md5(file_content) # SAFE: File checksums, caching
hashlib.md5(password) # FLAG: Password hashing
random.random() # SAFE: Non-security uses (UI, sampling)
random.random() for token # FLAG: Security tokens need secrets moduleOutput Format
## Security Review: [File/Component Name]
### Summary
- **Findings**: X (Y Critical, Z High, ...)
- **Risk Level**: Critical/High/Medium/Low
- **Confidence**: High/Mixed
### Findings
#### [VULN-001] [Vulnerability Type] (Severity)
- **Location**: `file.py:123`
- **Confidence**: High
- **Issue**: [What the vulnerability is]
- **Impact**: [What an attacker could do]
- **Evidence**:
```python
[Vulnerable code snippet]Fix: [How to remediate]
Needs Verification
[VERIFY-001] [Potential Issue]
Location:
file.py:456Question: [What needs to be verified]
If no vulnerabilities found, state: "No high-confidence vulnerabilities identified."
---
## Reference Files
### Core Vulnerabilities (`references/`)
| File | Covers |
|------|--------|
| `injection.md` | SQL, NoSQL, OS command, LDAP, template injection |
| `xss.md` | Reflected, stored, DOM-based XSS |
| `authorization.md` | Authorization, IDOR, privilege escalation |
| `authentication.md` | Sessions, credentials, password storage |
| `cryptography.md` | Algorithms, key management, randomness |
| `deserialization.md` | Pickle, YAML, Java, PHP deserialization |
| `file-security.md` | Path traversal, uploads, XXE |
| `ssrf.md` | Server-side request forgery |
| `csrf.md` | Cross-site request forgery |
| `data-protection.md` | Secrets exposure, PII, logging |
| `api-security.md` | REST, GraphQL, mass assignment |
| `business-logic.md` | Race conditions, workflow bypass |
| `modern-threats.md` | Prototype pollution, LLM injection, WebSocket |
| `misconfiguration.md` | Headers, CORS, debug mode, defaults |
| `error-handling.md` | Fail-open, information disclosure |
| `supply-chain.md` | Dependencies, build security |
| `logging.md` | Audit failures, log injection |
### Language Guides (`languages/`)
- `python.md` - Django, Flask, FastAPI patterns
- `javascript.md` - Node, Express, React, Vue, Next.js
### Infrastructure (`infrastructure/`)
- `docker.md` - Container securityFiles
- ATTRIBUTION.mdAdded by AutoGineer902 B
- LICENSE884 B
- SKILL.md11.5 KiB
- SPEC.md8.8 KiB
- infrastructure/docker.md9.2 KiB
- languages/javascript.md9.8 KiB
- languages/python.md9.3 KiB
- references/api-security.md12.4 KiB
- references/authentication.md8.9 KiB
- references/authorization.md9.8 KiB
- references/business-logic.md12.4 KiB
- references/cryptography.md8.5 KiB
- references/csrf.md9.7 KiB
- references/data-protection.md9.3 KiB
- references/deserialization.md10.0 KiB
- references/error-handling.md11.4 KiB
- references/file-security.md12.1 KiB
- references/injection.md6.7 KiB
- references/logging.md11.7 KiB
- references/misconfiguration.md10.1 KiB
- references/modern-threats.md13.0 KiB
- references/ssrf.md10.5 KiB
- references/supply-chain.md8.9 KiB
- references/xss.md7.4 KiB
references/file-security.md
File Security Reference
Overview
File operations present multiple security risks: path traversal attacks, malicious file uploads, XML External Entity (XXE) attacks, and insecure file permissions. This reference covers secure patterns for handling files.
Path Traversal Prevention
The Vulnerability
# VULNERABLE: User-controlled path
@app.route('/download')
def download():
filename = request.args.get('file')
return send_file(f'/uploads/{filename}')
# Attack: ?file=../../../etc/passwd
# Results in: /uploads/../../../etc/passwd → /etc/passwdPrevention Techniques
import os
from pathlib import Path
# Method 1: Validate and canonicalize path
def safe_join(base_directory, user_path):
"""Safely join paths, preventing traversal."""
# Resolve to absolute path
base = Path(base_directory).resolve()
target = (base / user_path).resolve()
# Verify target is under base
if not str(target).startswith(str(base)):
raise ValueError("Path traversal detected")
return str(target)
# Method 2: Use allowlist of files
ALLOWED_FILES = {'report.pdf', 'manual.pdf', 'readme.txt'}
def download_file(filename):
if filename not in ALLOWED_FILES:
raise ValueError("File not allowed")
return send_file(os.path.join(UPLOAD_DIR, filename))
# Method 3: Use indirect references
def get_file_by_id(file_id):
# Map ID to filename in database
file_record = File.query.get(file_id)
if not file_record or file_record.user_id != current_user.id:
raise PermissionError()
return send_file(file_record.storage_path)Characters to Block
# Dangerous path patterns
BLOCKED_PATTERNS = [
'..', # Parent directory
'~', # Home directory
'%2e%2e', # URL-encoded ..
'%252e%252e', # Double-encoded ..
'..\\', # Windows backslash
'..%5c', # URL-encoded Windows
'%00', # Null byte (older systems)
]
def contains_traversal(path):
path_lower = path.lower()
return any(pattern in path_lower for pattern in BLOCKED_PATTERNS)File Upload Security
Defense in Depth Approach
import magic
import hashlib
import uuid
from pathlib import Path
# Configuration
ALLOWED_EXTENSIONS = {'pdf', 'png', 'jpg', 'jpeg', 'gif'}
ALLOWED_MIMETYPES = {
'application/pdf',
'image/png',
'image/jpeg',
'image/gif'
}
MAX_FILE_SIZE = 10 * 1024 * 1024 # 10MB
UPLOAD_DIR = '/var/uploads' # Outside webroot
def secure_upload(file):
"""Comprehensive file upload validation."""
# 1. Check file size
file.seek(0, 2) # Seek to end
size = file.tell()
file.seek(0) # Reset
if size > MAX_FILE_SIZE:
raise ValueError(f"File too large: {size} bytes")
# 2. Validate extension
original_filename = file.filename
extension = Path(original_filename).suffix.lower().lstrip('.')
if extension not in ALLOWED_EXTENSIONS:
raise ValueError(f"Extension not allowed: {extension}")
# 3. Validate MIME type (don't trust Content-Type header)
mime = magic.from_buffer(file.read(2048), mime=True)
file.seek(0)
if mime not in ALLOWED_MIMETYPES:
raise ValueError(f"MIME type not allowed: {mime}")
# 4. Validate extension matches content
expected_extensions = get_extensions_for_mime(mime)
if extension not in expected_extensions:
raise ValueError("Extension doesn't match content type")
# 5. Generate safe filename (ignore user input)
safe_filename = f"{uuid.uuid4().hex}.{extension}"
# 6. Store outside webroot
storage_path = os.path.join(UPLOAD_DIR, safe_filename)
file.save(storage_path)
# 7. Set restrictive permissions
os.chmod(storage_path, 0o640)
return {
'original_name': original_filename,
'stored_name': safe_filename,
'storage_path': storage_path,
'size': size,
'mime_type': mime
}Filename Sanitization
import re
import unicodedata
def sanitize_filename(filename):
"""Sanitize filename for safe storage."""
# Normalize unicode
filename = unicodedata.normalize('NFKD', filename)
# Remove path components
filename = os.path.basename(filename)
# Remove null bytes
filename = filename.replace('\x00', '')
# Allow only safe characters
filename = re.sub(r'[^a-zA-Z0-9._-]', '_', filename)
# Prevent hidden files
filename = filename.lstrip('.')
# Limit length
if len(filename) > 255:
name, ext = os.path.splitext(filename)
filename = name[:255-len(ext)] + ext
return filename or 'unnamed'Image Validation
from PIL import Image
import io
def validate_image(file_data):
"""Validate and reprocess image to strip metadata/payloads."""
try:
# Verify it's a valid image
img = Image.open(io.BytesIO(file_data))
img.verify()
# Reopen for processing (verify closes the file)
img = Image.open(io.BytesIO(file_data))
# Convert to remove potential embedded content
output = io.BytesIO()
img.save(output, format=img.format)
output.seek(0)
return output.read()
except Exception as e:
raise ValueError(f"Invalid image: {e}")Dangerous File Types
# Never allow execution
DANGEROUS_EXTENSIONS = {
# Executables
'exe', 'dll', 'so', 'dylib', 'bin',
# Scripts
'php', 'php3', 'php4', 'php5', 'phtml',
'asp', 'aspx', 'ascx', 'ashx',
'jsp', 'jspx',
'cgi', 'pl', 'py', 'rb', 'sh', 'bash',
# Server config
'htaccess', 'htpasswd',
'config', 'ini',
# HTML (XSS risk)
'html', 'htm', 'xhtml', 'svg',
# Office macros
'docm', 'xlsm', 'pptm',
}
# Dangerous MIME types
DANGEROUS_MIMETYPES = {
'application/x-executable',
'application/x-msdownload',
'application/x-php',
'text/html',
'image/svg+xml', # Can contain scripts
}XML External Entity (XXE) Prevention
The Vulnerability
<!-- Malicious XML -->
<?xml version="1.0"?>
<!DOCTYPE foo [
<!ENTITY xxe SYSTEM "file:///etc/passwd">
]>
<data>&xxe;</data>Python Prevention
# VULNERABLE: Default lxml settings
from lxml import etree
doc = etree.parse(untrusted_file) # XXE enabled by default
# SAFE: Disable external entities
from lxml import etree
parser = etree.XMLParser(
resolve_entities=False,
no_network=True,
dtd_validation=False,
load_dtd=False
)
doc = etree.parse(untrusted_file, parser)
# SAFE: defusedxml library (recommended)
import defusedxml.ElementTree as ET
doc = ET.parse(untrusted_file) # XXE disabled by defaultJava Prevention
// VULNERABLE: Default DocumentBuilder
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.parse(untrustedFile);
// SAFE: Disable dangerous features
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true);
dbf.setFeature("http://xml.org/sax/features/external-general-entities", false);
dbf.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
dbf.setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false);
dbf.setXIncludeAware(false);
dbf.setExpandEntityReferences(false);
DocumentBuilder db = dbf.newDocumentBuilder();.NET Prevention
// SAFE in .NET 4.5.2+: XmlReader is safe by default
XmlReader reader = XmlReader.Create(stream);
// For older versions, explicitly disable
XmlReaderSettings settings = new XmlReaderSettings();
settings.DtdProcessing = DtdProcessing.Prohibit;
settings.XmlResolver = null;
XmlReader reader = XmlReader.Create(stream, settings);Archive (ZIP) Handling
Zip Slip Prevention
import zipfile
import os
def safe_extract(zip_path, extract_dir):
"""Safely extract ZIP, preventing path traversal."""
extract_dir = os.path.abspath(extract_dir)
with zipfile.ZipFile(zip_path, 'r') as zf:
for member in zf.namelist():
# Get absolute path of extracted file
member_path = os.path.abspath(os.path.join(extract_dir, member))
# Verify it's under extract directory
if not member_path.startswith(extract_dir + os.sep):
raise ValueError(f"Path traversal in ZIP: {member}")
# Check for symlinks (additional safety)
if member.endswith('/'):
os.makedirs(member_path, exist_ok=True)
else:
os.makedirs(os.path.dirname(member_path), exist_ok=True)
with zf.open(member) as source, open(member_path, 'wb') as target:
target.write(source.read())Zip Bomb Prevention
MAX_UNCOMPRESSED_SIZE = 100 * 1024 * 1024 # 100MB
MAX_COMPRESSION_RATIO = 100
def check_zip_bomb(zip_path):
"""Detect potential zip bombs."""
compressed_size = os.path.getsize(zip_path)
with zipfile.ZipFile(zip_path, 'r') as zf:
uncompressed_size = sum(info.file_size for info in zf.infolist())
# Check total size
if uncompressed_size > MAX_UNCOMPRESSED_SIZE:
raise ValueError(f"Uncompressed size too large: {uncompressed_size}")
# Check compression ratio
if compressed_size > 0:
ratio = uncompressed_size / compressed_size
if ratio > MAX_COMPRESSION_RATIO:
raise ValueError(f"Suspicious compression ratio: {ratio}")
return TrueFile Permissions
Secure Defaults
import os
import stat
# Uploaded files: readable by app, not executable
def secure_file_permissions(path):
os.chmod(path, stat.S_IRUSR | stat.S_IWUSR | stat.S_IRGRP) # 640
# Directories: accessible by app
def secure_directory_permissions(path):
os.chmod(path, stat.S_IRWXU | stat.S_IRGRP | stat.S_IXGRP) # 750
# Sensitive files: only owner
def sensitive_file_permissions(path):
os.chmod(path, stat.S_IRUSR | stat.S_IWUSR) # 600Temporary Files
import tempfile
import os
# VULNERABLE: Predictable temp file
with open('/tmp/myapp_temp.txt', 'w') as f:
f.write(sensitive_data)
# SAFE: Secure temp file
with tempfile.NamedTemporaryFile(mode='w', delete=False) as f:
f.write(sensitive_data)
temp_path = f.name
# File has restrictive permissions automatically
# SAFE: Temp directory
with tempfile.TemporaryDirectory() as tmpdir:
# Directory and contents deleted on exit
passGrep Patterns for Detection
# Path traversal risks
grep -rn "open(.*request\|send_file(.*request" --include="*.py"
grep -rn "fs\.readFile.*req\|fs\.writeFile.*req" --include="*.js"
# Dangerous file operations
grep -rn "os\.system.*file\|subprocess.*file" --include="*.py"
# XML parsing (XXE risk)
grep -rn "etree\.parse\|xml\.parse\|DOM\.parse" --include="*.py" --include="*.java"
grep -rn "XMLReader\|DocumentBuilder" --include="*.java"
# ZIP handling
grep -rn "zipfile\|ZipFile\|extractall" --include="*.py" --include="*.java"
# File permissions
grep -rn "chmod 777\|chmod 666\|chmod 755" --include="*.py" --include="*.sh"Testing Checklist
[ ] Path traversal prevented (canonicalization + validation)
[ ] File extensions validated against allowlist
[ ] MIME types validated (not just Content-Type header)
[ ] Filenames sanitized (don't use user input directly)
[ ] Files stored outside webroot
[ ] Restrictive file permissions set
[ ] Upload size limits enforced
[ ] Dangerous file types blocked
[ ] XML parsing has XXE disabled
[ ] ZIP extraction validates paths
[ ] ZIP bomb detection in place
[ ] Temporary files handled securely
References
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools, Needs an API key, Needs Python
Security
What our scanner noticed· Medium risk
- References to credential files
- Instructions that use the network
- Encoded commands that are executed
- Downloads piped into a shell
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Sentry
- Publisher
- Sentry (Official)
- Source
- getsentry/skills · skills/security-review · commit e94f222
- Licence
- Creative Commons Attribution-ShareAlike 4.0 International (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Sentry.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download security-review.zip