Security audit
Security checks for vulnerabilities and agentic risk
This is a normal batch file renamer with dry-run safeguards, but it under-declares its file/system permissions while it can rename local files.
Review before installing because the skill can rename files when --apply is used, and its permissions metadata currently understates that capability. Use dry-run first, limit --dir to a folder you intend to modify, and back up important files before applying changes.
The manifest declares filesystem: false while the skill’s stated purpose, CLI entry point, allowed tools, and documented --apply behavior all require reading and renaming files. This mismatch can bypass policy gating, mislead operators about the skill’s effective privileges, and cause the skill to be approved or executed under false security assumptions.
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
### Usage
- Main script: `python batch_renamer.py`.
- Key params: prefix/suffix strings; find-replace rule for wildcard text; extension whitelist.
- Execution control: preview-only by default; `--apply` actually renames.
### Flow
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
### Flow
1. Load the target directory; auto-scan all files/subfiles.
2. Virtually compute new names per prefix/suffix/replace rules.
3. Confirm the filtered extension list covers the intended types.
4. Print the rename preview list; wait for human confirmation.
5. On approval, apply `--apply` to actually rename files.
The title and opening guidance present the skill documentation entirely in Chinese and direct readers to other materials without indicating any language choice. This can violate language/locale policy when a skill forces a specific language for use or maintenance without explicit opt-in or justification.
The title presents Chinese first and the document foregrounds Chinese content, which can indicate a default language preference. Under the stated policy, language constraints should either offer user choice or be clearly justified as region-specific; this file does not document such a justification.
The top-level description is presented only in Chinese and does not indicate that language selection depends on user preference. Because this is natural-language behavior visible in the skill definition, it creates a locale/language policy issue unless the user is given a choice or the regional constraint is justified.
The changelog explicitly says 'Bilingual rewrite (full EN+ZH, English first)', which imposes a preferred language ordering in the skill's natural-language presentation. This can conflict with organizational language/locale policies when no user opt-in or preference handling is specified.