← Back to Directory
🍳
Security Audit Automator
Run automated security scans: check for vulnerable packages, open ports, weak permissions, outdated software. Generate compliance reports.
🤖 0 ↑ 0 ↓ | 👤 0 ↑ 0 ↓
advanced⏱ 30 min setup🔄 5 swappable alternatives
🧂 Ingredients
🔌 APIs
check_dependabot_alerts_and_advisory_database
🔄 Alternatives:
Gitlab — Built-in CI/CD, self-hostableBitbucket — Atlassian ecosystem integration
Send security findingsrequired
send_security_findings
🔄 Alternatives:
Discord — Free, great for communitiesTelegram — Simple bot API, no approval neededTeams — Enterprise/Office 365 integration
📋 Step-by-Step Build Guide
STEP 1
Run npm audit / pip audit on project dependencies
Run npm audit / pip audit on project dependencies
Run npm audit / pip audit on project dependencies Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
STEP 2
Check for known CVEs in installed packages
Check for known CVEs in installed packages
Check for known CVEs in installed packages Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
STEP 3
Scan for open ports with netstat/ss
Scan for open ports with netstat/ss
Scan for open ports with netstat/ss Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
STEP 4
Check file permissions on sensitive config files
Check file permissions on sensitive config files
Check file permissions on sensitive config files Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
STEP 5
Verify firewall rules are as expected
Verify firewall rules are as expected
Verify firewall rules are as expected Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
STEP 6
Generate security report with severity ratings
Generate security report with severity ratings
Compile the gathered data into a structured report. Format as clean Markdown with: - Title/date header - Executive summary (2-3 sentences) - Key metrics section with actual numbers - Detailed sections with bullet points - Action items or recommendations at the end Keep it scannable — busy people read reports in 30 seconds. Use emoji sparingly for visual anchors (📊 metrics, ✅ wins, ⚠️ concerns, 📋 action items). Include data comparisons: "X this period vs Y last period (↑Z%)" If any data source was unavailable, note it clearly: "⚠️ [Source] data unavailable — excluded from this report."
STEP 7
Alert on critical/high findings immediately
Alert on critical/high findings immediately
Alert on critical/high findings immediately Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
🤖 Example Agent Prompt
Run npm audit / pip audit on project dependencies Steps: 1. Validate all required inputs are available 2. Execute the operation described above 3. Verify the result meets expected output format 4. Handle errors gracefully — retry transient failures, log and alert on persistent ones 5. Return structured output with status and any relevant data If any required data is missing, request it from the user before proceeding.
Copy this prompt into your agent to get started.