Security audit

Incident

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only incident response workflow with no code execution, data access, persistence, or hidden behavior.

This skill is safe to install for structured incident response help. Users should know it may offer the incident workflow in adjacent contexts like reviews or stakeholder updates, but it should ask before applying the workflow and does not gain special access or run code.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (1)

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 92% confidence
Finding: The trigger guidance includes broad phrases like 'closely related work' and contexts such as 'preparing a review, rollout, or stakeholder communication' without clear boundaries or exclusion conditions. In a markdown skill description, this can overlap with many ordinary engineering conversations and make invocation criteria unclear.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.