T09 · Insecure Skill Coding Practices
- Location
scripts/extract-tokens.js:25- Finding
Chromium Sandbox Disabled for Attacker-Controlled Web Content
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent design-extraction purpose, but it opens arbitrary websites in an unsandboxed browser and does not restrict internal URLs or output paths.
Install only if you are comfortable with a skill that opens and executes JavaScript from the URL you provide. Use it only on public or authorized sites, avoid authenticated or internal pages, and run it in an isolated environment with a dedicated output directory until sandboxing, URL validation, and overwrite protections are added.
scripts/extract-tokens.js:25Chromium Sandbox Disabled for Attacker-Controlled Web Content
scripts/extract-tokens.js:14Unrestricted URL Navigation Enables Internal and Local Resource Access
scripts/extract-tokens.js:16Unrestricted Output Path Allows Overwriting Arbitrary Writable Files
The README explicitly states the skill captures live websites via browser, including screenshots and DOM snapshots, but provides no warning about privacy, authorization, or handling of potentially sensitive page content. In practice, users may point this at authenticated, internal, or personal pages, causing collection and persistence of sensitive UI data, tokens rendered in-page, or proprietary design assets without informed consent or clear safeguards.
Marketing the tool as a one-click way to extract the design language of 'any website' encourages broad scraping behavior without disclosing privacy, copyright, permission, or acceptable-use constraints. In the context of a skill designed to reverse-engineer visual systems, this omission increases the chance of misuse against non-public, restricted, or legally protected content.
The README states the skill will load arbitrary websites, take screenshots, capture DOM snapshots, and extract CSS, but it does not warn users about privacy, data handling, authorization, or site-specific restrictions. This can lead operators to collect sensitive page contents or process protected material without realizing the legal, privacy, or policy implications.
The skill advertises broad trigger phrases like 'extract design system' and 'capture the look of a website', which can cause the agent to invoke it in situations where the user did not clearly consent to browsing a third-party URL and extracting site data. Because the skill performs external navigation and token extraction, accidental invocation increases the chance of unintended network access and data collection.
The workflow instructs the agent to navigate to an arbitrary target URL, take screenshots, snapshot the page, and run a token-extraction script, but the skill description does not warn users that it will access external websites and collect design data from them. This is dangerous because users may unknowingly trigger network access to sensitive, internal, authenticated, or otherwise non-public pages, leading to unintended exposure of visual and structural information.
The script accepts an arbitrary user-supplied URL and automatically opens it in a headless browser, executing page JavaScript and collecting computed style data from the visited page. In an agent/automation context, this can trigger unintended outbound network access to internal or sensitive endpoints, leak browsing metadata, and capture more page-derived information than a user may expect, even though the intended purpose is design-token extraction.
The output section says the generated DESIGN.md should be saved to a user-specified target location, with optional preview files, but it does not clearly warn that the skill writes files to disk. Unclear file-write behavior can cause accidental overwrites, placement in sensitive directories, or unexpected artifact creation, especially when combined with optional HTML outputs.
No suspicious patterns detected.