Security audit

Incident Response Playbook

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed markdown-only incident response guide with no executable code, but users should treat its security and outage guidance as draft support rather than authority.

Install only if you want playbook-style incident response drafting. Do not paste secrets, credentials, regulated personal data, or privileged incident details unless your agent environment is approved for that data, and have qualified security, legal, privacy, or operations staff validate recommendations before taking real-world action.

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 (2)

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The README promotes use for breaches, unauthorized access, data loss, privacy incidents, and outage response, but does not warn that outputs may affect sensitive security, privacy, legal, and business-critical decisions. Without disclaimers and safety boundaries, users may provide confidential incident data or treat generated guidance as authoritative during high-stakes events, which can amplify harm if the advice is incomplete, incorrect, or noncompliant.

Vague Triggers

Medium

Confidence: 91% confidence
Finding: The quick-start tells users to broadly 'describe your incident to your agent' and says the agent 'handles triage, response coordination, and post-mortem documentation' without defining scope limits, required human approval, or constraints for sensitive actions. In an incident-response context, this can encourage overreliance on AI during security, privacy, or operational emergencies, increasing the chance of unsafe guidance, disclosure of sensitive data, or inappropriate autonomous decision-making.

Static analysis

No suspicious patterns detected.