← ClaudeAtlas

grab-cookielisted

Capture, store, wire, and verify a browser-session credential for any site that has no API key and no OAuth path: an httpOnly session cookie, an opaque localStorage bearer token, or a custom auth header. The human step is one DevTools "Copy as cURL" paste, and everything around it is automated: parse the request, extract the secret per a per-site JSON profile, store it in the Windows Credential Manager or the macOS Keychain without the value entering the agent's context, regenerate whatever config file consumes it, and prove the result with a real authenticated call. A daily doctor re-probes every stored credential and warns before a known expiry instead of after. Use when the user says a tool stopped working after about a month, my session expired, re-auth this site, the cookie died again, refresh my token, this vendor has no API key, or set up auth for a site that only works when logged in. This Skill does NOT drive a browser. It reads a cURL command the user pastes. For vendors that DO expose OAuth or an A
Servosity/msp-skills · ★ 82 · AI & Automation · score 80
Install: claude install-skill Servosity/msp-skills
# grab-cookie - session credentials for sites with no API path Some vendors never issue an API key. Their web app authenticates with an httpOnly session cookie or an opaque token in localStorage, and the only way to reach the API your agent needs is to borrow the session the browser already has. That capture is irreducibly human: an httpOnly cookie is invisible to page JavaScript by design, and a headless browser does not carry your login. What is NOT irreducible is everything around it. This Skill automates the rest, so a thirty-day re-auth costs one paste instead of an afternoon of remembering where the token was supposed to go. ## When to use this Skill, and when not to Use it when the vendor has no API-key or OAuth path for the surface you need, and the working credential exists only inside a logged-in browser session. Do not use it when the vendor does issue an API key or supports OAuth. The `connect-tool` Skill in this repository handles those properly, including scope changes and rotation. `connect-tool` deliberately refuses cookie import and never reads `document.cookie` or `localStorage`, which is the correct choice for its threat model. This Skill covers the case that choice leaves open, and it makes the opposite tradeoff explicitly. ## 0. Running the helpers Every helper is a stdlib Python script next to this file. Python 3.12 or newer, no third-party packages, no compiled binary, no MCP server: ```bash python "<this-skill-dir>/scripts/credgrab.py" <command