security-audit
Review security of command execution, tool permissions, and API key handling. Use when user mentions "security review", "audit", "check security", "vulnerabilities", or before deploying to production.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
Security Audit
Instructions
-
Command Execution Review (
backend/main.py):- Check
run_terminal_command()for shell injection vulnerabilities - Verify timeout is enforced (should be 15 seconds)
- Look for dangerous command patterns
- Check
-
Tool Permission Review:
- Verify Chat mode only allows:
read_file,web_search - Check Agent mode tool restrictions
- Look for permission bypass vulnerabilities
- Verify Chat mode only allows:
-
Secrets Management:
- Ensure
.envis in.gitignore - Check no API keys are hardcoded
- Verify
python-dotenvusage for environment variables
- Ensure
-
WebSocket Security:
- Check for authentication on
/wsendpoint - Review message validation
- Look for injection points in user input
- Check for authentication on
-
Frontend Security:
- Check for XSS in markdown rendering
- Review image upload handling (base64 encoding)
- Verify no sensitive data in client-side code
-
Generate report with:
- Critical issues (immediate action required)
- Warnings (should fix before production)
- Recommendations (best practices)
Examples
- "Run a security audit"
- "Check for vulnerabilities"
- "Review security before deploy"
Guardrails
- This is a READ-ONLY audit; do not modify files
- Report findings without exploiting vulnerabilities
- Recommend fixes but get user approval before implementing
- Never log or expose discovered secrets
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-28
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!