agentsclimarketplace
Sign in

Security scan

Skill opsera-agents/opsera-devsecops/skills/security-scan

Technical security scanning for vulnerabilities, secrets, SAST, container security, and infrastructure-as-code issues. Use when the user asks for vulnerability scanning, secret detection, code security analysis, container scanning, or IaC security checks.From its SKILL.md

Install
npx -y skills add opsera-agents/opsera-devsecops --skill security-scan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, as published. Nobody here has run it

Security Scan

Perform a comprehensive security scan using the mcp__opsera__security-scan tool.

When to Trigger

  • User asks to "scan for vulnerabilities", "find secrets", or "security scan"
  • User wants SAST analysis, container scanning, or IaC security checks
  • User asks "is this code secure?" or "check for security issues"

Execution Steps

  1. Collect inputs (Phase 1): Ask the user for any missing required parameters:
    • path: Directory or repo to scan (ask if not specified)
    • scan_type: full, secrets, vulnerabilities, sast, containers, or iac (ask if not specified)
    • severity_threshold: critical, high, medium, or all (ask if not specified)
  2. Verify tools (Phase 2): Check that required scanning tools are installed. Call with phase: 2 and tools_ready once verified. If tools are missing, help the user install them or note skipped tools.
  3. Execute scans (Phase 3): Run the actual security scans. Call with phase: 3.
  4. Generate reports (Phase 4): Create markdown and HTML reports with findings. Call with phase: 4 and scan_results.
  5. Report telemetry (Phase 5): Call mcp__opsera__opsera_report_telemetry with:
    • toolName: security-scan
    • status: success/partial/failed
    • target: the path scanned
    • targetType: repository/container/code
    • Finding counts: critical, high, medium, low, total
  6. Complete (Phase 6): Present the summary with critical findings first, remediation steps, and suggested follow-up actions.

Important

  • NEVER assume tools_ready=true without actually checking
  • NEVER skip asking for missing parameters
  • ALWAYS report telemetry after scan completion

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.