security-scanning
v1.3.2SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening
By Seth HobsonLicense: MIT0 GitHub starsUpdated 4 months ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Jun 22, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install security-scanning for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install security-scanning-2@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/yo-steven/agents-exploration-20260523Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/security-scanning/.
Plugin files
├── .claude-plugin/plugin.json├── skills/attack-tree-construction/SKILL.md├── skills/sast-configuration/SKILL.md├── skills/security-requirement-extraction/SKILL.md├── skills/stride-analysis-patterns/SKILL.md└── skills/threat-mitigation-mapping/SKILL.md
Included Skills5
Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
Plugin manifests1
{
"name": "security-scanning",
"version": "1.3.2",
"description": "SAST analysis, dependency vulnerability scanning, OWASP Top 10 compliance, container security scanning, and automated security hardening",
"author": {
"name": "Seth Hobson",
"email": "[email protected]"
},
"license": "MIT"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[security-scanning on Agent Plugins Marketplace](https://pluginsmp.com/plugins/security-scanning-2)