T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:12- Finding
Excessive Filesystem and Command-Execution Permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does not show malicious behavior, but it asks for broad write and command-execution authority while advertising autonomous self-improvement and skill evolution without clear scope, safeguards, or implemented functionality.
Review before installing. This package does not currently perform the learning features it advertises, yet it requests powerful file and command-execution capabilities and is designed to run continuously. Install only in a tightly sandboxed environment unless the publisher narrows permissions, documents clear user controls, and aligns the implementation with the claims.
SKILL.md:12Excessive Filesystem and Command-Execution Permissions
The declared description promises a functional self-improving agent with autonomous learning, pattern extraction, confidence scoring, and skill evolution on a 17-minute loop. The code only implements the loop structure and phase timing/logging. Each phase contains placeholder comments and sleeps, with no real data capture, analysis, extraction, aggregation, or self-improvement behavior. The 17-minute loop aspect is represented, but the primary promised capabilities are absent, making the description materially overstated relative to actual behavior.
The skill advertises autonomous self-optimization, learning, and skill evolution while also declaring powerful tools such as Write, Bash, and Exec, yet it does not present a clear warning, consent model, or operational guardrails for file or system modifications. In this context, users may enable a highly privileged autonomous workflow without understanding that it could write files, execute commands, or alter system state if later implemented or interpreted literally by an agent.
The manifest description says the skill 'learns from every execution' and 'continuously optimizes itself' without specifying when it should be invoked, what scope of executions it applies to, or any exclusion conditions. For a manifest/markdown file, this is vague enough to risk unintended activation because it describes broad autonomous behavior rather than narrow, explicit triggers.
Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
- Write
- Bash
- Exec
model: sonnet
---
# Auto-Improver - 自动改进代理
The user-facing title, headings, descriptions, FAQ, and operational guidance are presented in Chinese, with no indication that another language can be selected or that the locale is required for a region-specific purpose. This creates a natural-language policy concern because the skill appears to impose a language choice without user opt-in.
The manifest description says the skill is an "Auto-improving AI agent that learns from every execution and continuously optimizes itself," but it does not define any concrete trigger conditions, scope boundaries, or exclusions. In a manifest file, this kind of broad self-improvement description can encourage unintended invocation because it implies applicability to nearly any execution context.
The manifest and module header describe substantive autonomous learning and self-optimization behavior, including learning from executions, pattern extraction, confidence scoring, and skill evolution. In the implementation, each phase only logs a message and waits for a configured duration, with TODO comments indicating the claimed learning and evolution logic is not actually implemented.
This code includes natural-language descriptions, comments, and user-facing console output in Chinese throughout the file, but provides no indication that the language is configurable or that the skill is intentionally limited to a Chinese-speaking context. Under the stated policy, forcing a specific language without user opt-in is a locale-policy violation.
The phase comments state that the code captures execution data, identifies patterns, generates instincts, and aggregates them into skills/commands/agents. However, the function bodies only print status messages, contain TODO placeholders, and sleep, so the comments actively overstate what the code currently does.
No suspicious patterns detected.