Back to skill

Security audit

batch-file-rename

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward batch-renaming guide, but users should add collision checks before running its example commands on important files.

Install only if you are comfortable reviewing shell commands before running them. Always run a dry-run first, back up important directories, and add explicit destination-collision checks or use no-clobber behavior before applying the examples to valuable or shared folders.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:55
Finding

Unsafe Rename Operations Can Silently Overwrite Existing Files

Content
View full analysis
Remediation
View remediation
&2 exit 1 fi mv -n -- "$f" "$new" ``` - Check both `-e` and `-L` so that dangling symbolic links are also treated as collisions. - Abort the entire batch before making changes when any conflict is found, rather than detecting conflicts after partial execution. - Preserve a manifest of original and destination names to support review and recovery. - Keep the documented dry-run requirement, but do not rely on manual review as the only collision control. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:72
Finding

Line-Delimited Recursive Traversal Misparses Filenames Containing Newlines

Content
View full analysis
Remediation
View remediation
&2 continue fi mv -n -- "$f" "$new" && printf '%s → %s\n' "$f" "$new" done ``` Where supported, an alternative is `find ... -exec` with safely quoted positional arguments. Retain `--` for utilities that support it, and combine safe pathname handling with explicit destination-collision validation. ]]>
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep