T09 · Insecure Skill Coding Practices
- Location
scripts/rename.py:93- Finding
Incorrect AST Source Offsets Can Corrupt Files During Rename Operations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This refactoring skill is not clearly malicious, but it can rewrite or restore files in ways that are broader and less safe than its documentation says.
Review before installing. Use only on a backed-up Git working tree, run dry-run commands first, avoid broad roots, and do not use undo with any backup ID you did not verify. Treat the advertised extract/inline/move/batch features and safety claims as unreliable until the implementation is fixed.
scripts/rename.py:93Incorrect AST Source Offsets Can Corrupt Files During Rename Operations
scripts/main.py:46Destructive Rename Is the Default Despite Documentation Claiming Default Preview
scripts/rename.py:251Unvalidated Backup Identifier Allows Restoration from Arbitrary Directories
This finding indicates the skill may only implement a narrow rename workflow while claiming to be a broad, safe refactoring assistant with suggestions, batch support, and multiple transformation types. Such overstatement can mislead operators into relying on automation that lacks the promised analysis and safety checks, causing widespread incorrect edits across a codebase.
This finding indicates the skill may only implement a narrow rename workflow while claiming to be a broad, safe refactoring assistant with suggestions, batch support, and multiple transformation types. Such overstatement can mislead operators into relying on automation that lacks the promised analysis and safety checks, causing widespread incorrect edits across a codebase.
This finding indicates the skill may only implement a narrow rename workflow while claiming to be a broad, safe refactoring assistant with suggestions, batch support, and multiple transformation types. Such overstatement can mislead operators into relying on automation that lacks the promised analysis and safety checks, causing widespread incorrect edits across a codebase.
The skill advertises and documents operations that read and modify project files, but it declares no explicit tool scope or permissions boundary. In an agent environment, missing scope metadata can allow the skill to be invoked with broader-than-expected file access, increasing the chance of unintended or unsafe repository modifications.
This code proceeds from preview directly to executing a multi-file rename operation once the command is run without --dry-run. Although it prints the planned changes, there is no interactive confirmation prompt or equivalent user acknowledgment immediately before the irreversible write phase, and the operation modifies user code across the project.
The skill content switches into Chinese for core usage instructions and feature descriptions, but does not state that the skill is Chinese-only or offer an alternative language/locale choice. This can violate the language/locale policy when users are implicitly forced into a specific language without opt-in.
No suspicious patterns detected.