chrome-cdp-controller

This skill appears to be what it says: a Puppeteer-based controller for a local Chrome instance. Before installing or running it, consider these precautions: - Only connect it to browsers you control. Running Chrome with remote debugging exposes a WebSocket that this tool will use; ensure the debugging port is bound to localhost and not reachable by others. - Audit any commands/JSON files you pass to the script. Commands can (a) upload local files you specify, (b) read and execute JavaScript files from disk (evaluate with file), and (c) capture network responses — all of which can be used to leak sensitive data if the commands are untrusted. - Run the controller against a dedicated browser profile or an isolated/testing profile when automating sites that require credentials or when testing untrusted scripts. - npm install will pull puppeteer-core and standard npm dependencies; use usual supply-chain hygiene (up-to-date Node, verify package source) if you're concerned about third-party dependency risks. - If you need higher assurance, review scripts/cdp_controller.js locally (it was included and implements the documented features) and avoid executing command files received from untrusted sources.