Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but its default browser automation can automatically accept cookie or consent prompts for the user.
Install only if you are comfortable with the skill automatically dismissing overlays during browser automation. For privacy-sensitive browsing or sites with legal terms, use auto_dismiss=False or review consent dialogs manually before allowing clicks.
This markdown file contains substantial user-facing instructional content in Chinese, including usage guidance and examples, while the manifest does not indicate that the skill is region-specific or Chinese-only. Under the language/locale policy, forcing a specific language without opt-in or justification is a natural-language policy violation.
The documentation explicitly promotes automatic dismissal of cookie banners and dialogs, including matching consent-related text such as 'accept', 'agree', and 'allow', without warning that this may submit legal/privacy choices on the user's behalf. In a browser automation skill, this is risky because it can silently grant tracking consent or dismiss important notices, causing unintended user actions and compliance/privacy issues.
The skill automatically clicks consent/accept buttons on detected cookie or consent banners without user confirmation, which can silently alter privacy choices and create unauthorized state changes on third-party sites. In an automation context, this may accept tracking, legal terms, or other prompts beyond the user's intent because matching is based on broad text heuristics such as 'accept', 'agree', 'allow', and 'ok'.
Natural-language strings in the module docstrings, comments, and CLI output are written in Chinese, which imposes a specific language choice on users without opt-in or justification. The file does not state that it is intended only for a Chinese-speaking or region-specific audience.
The inline comment at L125 says the code searches for buttons containing × or Close text, and L131 says it returns null 'but marks text match found'. In actual behavior, this function has no separate marker or side channel; it simply returns null, so callers cannot distinguish 'found by text' from 'not found at all'. This is a documentation-to-code contradiction, albeit low impact.
