Back to skill

Security audit

Loop Skill

Security checks for vulnerabilities and agentic risk

Overview

The skill openly automates multi-repository coding work, but it can read projects, write plan files, start a persistent loop, and dispatch worker CLIs without a clear confirmation checkpoint.

Install only if you intentionally want an agent to read selected repositories, create or update planning files, start a background dashboard and loop, and dispatch coding CLI workers. Use a narrow project root, review generated plans before allowing workers to run, and make sure you know how to stop it with the documented down command.

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

The trigger phrases are broad enough that ordinary user requests about '推进项目', '后台常驻', or '自动推进计划' could unintentionally activate a powerful orchestration skill. In this skill’s context, accidental invocation is more dangerous because activation leads directly to repository scanning, plan generation, file writes, and background loop startup without an explicit confirmation gate.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

This section instructs unattended ingestion and startup of a persistent background loop after writing or updating repository files, while explicitly telling the controller not to ask follow-up questions. That combination removes informed consent for actions that modify project files, launch long-running services, and dispatch downstream agents, increasing the risk of unintended changes, resource consumption, and hard-to-stop automation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.