Back to skill

Security audit

Ai Adoption Readiness

Security checks for vulnerabilities and agentic risk

Overview

This is a markdown-only planning skill that asks for relevant business context to produce an AI readiness report, with no hidden execution or persistence behavior found.

You can install this as a planning aid, but avoid sharing confidential budgets, internal systems, or sensitive blockers unless the agent environment is approved for that business information. Treat its output as advisory strategy, not a substitute for compliance, security, or executive review.

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
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
95% confidence
Finding

The instruction 'Tell the agent about your organization and what AI initiative you're planning. It handles the rest.' does not define a specific invocation phrase or clear activation boundaries. This broad wording could overlap with ordinary conversation about an organization or AI plans, increasing the risk of unintended invocation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.