setup-browser-cookies
“Import cookies from your real Chromium browser into the headless browse session. (gstack)”
aipkg.jsonLICENSE.txtREADME.mdSKILL.mdSKILL.md.tmpl- 01SQP-285%MEDIUM
SKILL.md:153
detailhide
File write operations to user config directories (~/.gstack/) occur without explicit user confirmation. While the skill documents these writes in help text, there is no inline confirmation before destructive operations like removing files or modifying configuration. An attacker who can control the skill invocation or environment variables could cause unintended data loss or configuration corruption.
151Always run (regardless of choice):152```bash153rm -f ~/.gstack/.writing-style-prompt-pending154touch ~/.gstack/.writing-style-prompted155```fix Add explicit AskUserQuestion confirmations before any destructive file operations (rm, git rm). For config writes, show what will be changed and require affirmative user consent. At minimum, log all write operations with paths and require a --force flag for batch operations.
- 02PE3Credential Access85%HIGH
SKILL.md.tmpl:84
detailhide
The skill provides a mechanism to extract sensitive authentication credentials (cookies) from a user's real browser and import them into a headless session. While the stated purpose is legitimate QA testing, the skill creates a vector for credential harvesting. An attacker could invoke this skill to exfiltrate authenticated session cookies to unauthorized contexts, particularly if the browse session is later compromised or if cookie handling is not properly isolated.
## Notes - On macOS, the first import per browser may trigger a Keychain dialog — click "Allow" / "Always Allow" - On Linux, `v11` cookies may require `secret-tool`/libsecret access; `v10` cookies use Chromium's standard fallback key - Cookie picker is served on the same port as the browse server (no extra process) - Only domain names and cookie counts are shown in the UI — no cookie values are exposedfix Add explicit security warnings in the skill preamble clarifying: (1) what data will be accessed (browser credentials/cookies), (2) that users should only use this in trusted environments, (3) that imported cookies should be treated as sensitive and the session should be isolated, (4) add a confirmation dialog before cookie import begins asking the user to explicitly consent to cookie extraction, (5) document any limitations on cookie scope and lifecycle to prevent long-term persistence of sensitive credentials.