An assortment of security operations skills for AI coding agents. A collaborative approach to shift-left security using Claude Code skills.
SecOpsAgentKit provides specialized Claude Code skills for security operations, covering:
- Application Security (AppSec): SAST/DAST, vulnerability analysis, secure code review
- DevSecOps: CI/CD security, infrastructure as code security, container scanning
- Secure SDLC: Threat modeling, security requirements, secure design patterns
- Compliance: Security auditing, policy enforcement, compliance frameworks
- Incident Response: Security event analysis, forensics, remediation workflows
/plugin marketplace add https://github.com/AgentSecOps/SecOpsAgentKit.git
- api-mitmproxy - Interactive HTTPS proxy for API security testing with mitmproxy traffic interception and modification
- api-spectral - API specification linting and security validation using Spectral for OpenAPI and AsyncAPI
- dast-ffuf - Fast web fuzzer using ffuf for directory enumeration and parameter fuzzing
- dast-nuclei - Fast, template-based vulnerability scanning using ProjectDiscovery's Nuclei
- dast-zap - Dynamic application security testing using OWASP ZAP (Zed Attack Proxy)
- sast-bandit - Python security vulnerability detection using Bandit SAST with CWE and OWASP mappings
- sast-semgrep - Static application security testing using Semgrep for vulnerability detection
- sca-blackduck - Software Composition Analysis using Synopsys Black Duck for dependency vulnerabilities and license compliance
- container-grype - Container vulnerability scanning and dependency risk assessment using Grype with CVSS, EPSS, and CISA KEV prioritization
- container-hadolint - Dockerfile security linting and best practice validation using Hadolint
- iac-checkov - Infrastructure as Code security scanning using Checkov with 750+ built-in policies
- sca-trivy - Software Composition Analysis and container vulnerability scanning using Trivy for CVE detection
- secrets-gitleaks - Hardcoded secret detection and prevention in git repositories using Gitleaks
- reviewdog - Automated code review and security linting integration for CI/CD pipelines using reviewdog
- sast-horusec - Multi-language static application security testing using Horusec (18+ languages, 20+ tools)
- sbom-syft - Software Bill of Materials (SBOM) generation using Syft for container images and filesystems
- policy-opa - Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA)
- detection-sigma - Generic detection rule creation and management using Sigma (universal SIEM rule format)
- forensics-osquery - SQL-powered forensic investigation and system interrogation using osquery for endpoint analysis
- ir-velociraptor - Endpoint visibility and digital forensics using Velociraptor for incident response at scale
- pentest-metasploit - Penetration testing framework using Metasploit for exploit development and vulnerability validation
- recon-nmap - Network reconnaissance and security auditing using Nmap for port scanning and service detection
- network-netcat - Network utility using Netcat for reading/writing data across TCP/UDP connections and port scanning
- analysis-tshark - Network protocol analyzer and packet capture tool using tshark for traffic analysis
- webapp-sqlmap - Automated SQL injection detection and exploitation using SQLMap for web application security testing
- webapp-nikto - Web server vulnerability scanner using Nikto for identifying security issues and misconfigurations
- crack-hashcat - Advanced password recovery and hash cracking using Hashcat supporting multiple algorithms
Skills in this repository reference industry-standard security frameworks:
- OWASP - Open Web Application Security Project
- CWE - Common Weakness Enumeration
- MITRE ATT&CK - Adversarial Tactics, Techniques & Common Knowledge
- NIST - National Institute of Standards and Technology
- SOC2 - Service Organization Control 2
- PCI-DSS - Payment Card Industry Data Security Standard
- GDPR - General Data Protection Regulation
We welcome contributions! Please read CONTRIBUTE.md for:
- Skill creation guidelines
- Frontmatter standards
- Quality requirements
- Submission process
To kickstart a new skill for this repo:
-
Initialize: Create a new skill from the template
./scripts/init_skill.sh my-skill-name appsec
-
Develop: Fill in
SKILL.mdand add bundled resourcesscripts/- Executable security toolsreferences/- Security framework documentationassets/- Templates and configurations
-
Validate: Run the validation script
./scripts/validate_skill.py skills/appsec/my-skill-name
-
Update Documentation:
- Add your skill to the README.md (this file) under the appropriate category
- Update
.claude-plugin/marketplace.jsonwith your skill path
-
Submit: Open a PR with the
[skill]tag
See CONTRIBUTE.md for detailed guidelines including the exact format for README.md entries.
All skills follow these requirements:
---
name: skill-name # kebab-case identifier
description: > # Comprehensive description with use cases
What the skill does and when to use it...
version: 0.1.0 # Semantic versioning
maintainer: github-username # Your GitHub username
category: appsec # Primary security domain
tags: [sast, owasp, security] # Searchable tags
frameworks: [OWASP, CWE] # Security frameworks referenced
---- Concise: Keep SKILL.md under 500 lines
- Tested: All scripts must be tested and working
- Secure: Include security considerations and safe defaults
- Documented: Clear instructions using imperative form
- Versioned: Follow semantic versioning (MAJOR.MINOR.PATCH)
scripts/init_skill.sh- Initialize a new skill from templatescripts/validate_skill.py- Validate skill structure and frontmatterskills/_template/- Base template for all new skills
This project uses dual licensing:
- Documentation (skills - markdown files): Creative Commons Attribution-ShareAlike 4.0 International (CC-BY-SA 4.0)
- Code (scripts, configurations): Dual-licensed under CC-BY-SA 4.0 and Mozilla Public License 2.0 (MPL 2.0)
This means:
- You can freely use, share, and adapt all content with attribution
- Skills must be shared under the same CC-BY-SA 4.0 license
- Code should be used under MPL 2.0
See LICENSE.md for full license texts and details.