Back to skill

Security audit

unCAGd

Security checks for vulnerabilities and agentic risk

Overview

This skill provides disclosed project decision memory behavior with user-gated validation and no evidence of hidden execution, exfiltration, or destructive actions.

Before installing, understand that this skill is meant to remember project decisions across sessions. Use it for repositories or long-running projects where that is helpful, and only validate memories when you are comfortable making them durable project context.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The instruction to use the skill whenever the user is working on a repo, software project, agent workflow, plugin, MCP server, or multi-step implementation is very expansive and lacks clear exclusion conditions. This makes activation scope ambiguous and likely to overlap with a large share of normal engineering conversations.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

Conditions such as 'the task is part of an ongoing project' and 'the user asks to continue, refine, implement, or fix something' are common in everyday development requests and do not clearly distinguish when retrieval should not occur. The list also lacks negative examples or tighter constraints, so the activation boundary is unclear.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.