Back to skill

Security audit

Class

Security checks for vulnerabilities and agentic risk

Overview

This is a static OOP reference skill whose bundled script only prints educational text and does not access data, network services, credentials, or persistence mechanisms.

This skill appears safe to install as a local programming reference. The only practical consideration is that it ships a shell script, so users should invoke the documented commands intentionally; the inspected script only prints static reference text.

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
  • Memory PoisoningPersistent Context Injection, Context Window Stuffing, Memory Manipulation
  • 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)

Persistent Context Injection

Medium
Category
Memory Poisoning
Confidence
80% confidence
Finding

Skill injects content designed to persist in agent memory or context across interactions. Persistent injection can alter agent behavior long after the initial interaction.

Content

Scanner excerpt · scripts/script.sh (reported line 412)May include surrounding context.

sh
Deep Inheritance Hierarchies:
  Animal → Mammal → Domestic → Pet → Dog → GoldenRetriever
  Problems: fragile, hard to understand, hard to change base
  Rule: max 3 levels deep
  Fix: flatten hierarchy, use composition, use interfaces

Static analysis

No suspicious patterns detected.