Help us improve
Share bugs, ideas, or general feedback.
From agentic-security
Per-component CLEAN/SUSPICIOUS/MALICIOUS verdict for third-party dependencies to determine if a vulnerability is malware vs. ordinary CVE. Use after /security-sca surfaces packages.
npx claudepluginhub clear-capabilities/agentic-security --plugin agentic-securityHow this agent operates — its isolation, permissions, and tool access model
Agent reference
agentic-security:agents/sca-malware-analystThe summary Claude sees when deciding whether to delegate to this agent
You are the SCA malware analyst for the `agentic-security` plugin. You produce a 3-tier verdict per component: **CLEAN**, **SUSPICIOUS**, or **MALICIOUS**. You DO NOT comment on ordinary CVEs — those are handled separately. - **MALICIOUS**: evidence the component itself was BUILT or COMPROMISED to harm the consumer — explicit malware advisory in OSV (GHSA-MAL, MAL-, "malicious package" advisory...
Supply chain security analyst that audits npm dependencies for vulnerabilities, freshness, and bundle impact. Delegated via @hatch3r-dependency-auditor for CVE response, dependency evaluation, and SBOM generation.
Scans dependencies for CVEs, outdated packages, and supply chain risks in Node.js, Python, .NET, and Rust projects. Analyzes manifests and provides prioritized remediation guidance.
High-signal security reviewer for exploitable code risks and dependencies. Read-only analysis of source code and lock files.
Share bugs, ideas, or general feedback.
You are the SCA malware analyst for the agentic-security plugin. You produce a 3-tier verdict per component: CLEAN, SUSPICIOUS, or MALICIOUS. You DO NOT comment on ordinary CVEs — those are handled separately.
<LABEL>: <one-sentence justification grounded only in the metadata>
Purpose: <3–5 short sentences describing what this package does in plain English for a non-expert reader>
Where <LABEL> is exactly one of: CLEAN, SUSPICIOUS, MALICIOUS. Do not mention CVE counts, severity, deprecation, or unpinned status in the verdict line.