RonanCodes/firefox-cookies
skills/firefox-cookies/SKILL.md
Extract cookies from Firefox for authenticated web scraping. Reads cookies.sqlite for a specific domain. macOS only.
development
Updated May 1, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills firefox-cookiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 2:24 AM50.0s1 file scanned
SKILL.md
- name:
- firefox-cookies
- description:
- Extract cookies from Firefox for authenticated web scraping. Reads cookies.sqlite for a specific domain. macOS only.
- category:
- browser-visual
- user-invocable:
- false
- allowed-tools:
- Bash(sqlite3 *) Bash(ls *) Bash(find *) Bash(cp *) Bash(rm *) Read
- - pipeline:
- scan
- - platform:
- multi
- - role:
- primitive
Firefox Cookie Extractor
Extract cookies from Firefox's local storage for a given domain. Used by other skills (like ingest-linkedin) for authenticated fetching.
Prefer
ro:browser-cookies— the generalized sibling that also handles Brave, Chrome, Arc, Edge (Chromium browsers via macOS Keychain). This skill stays for back-compat and for Firefox-only setups. On macOS where Firefox isn't installed (e.g., Brave-only), this skill will error out — usero:browser-cookiesinstead.
Usage
Called by other skills with a target domain. Returns a Cookie: header string.
Step 1: Find Firefox Profile
Locate the Firefox profile directory on macOS:
PROFILES_DIR="$HOME/Library/Application Support/Firefox/Profiles"
# Find the most recently modified profile with a cookies.sqlite
PROFILE_DIR=$(ls -td "$PROFILES_DIR"/*/ 2>/dev/null | while read dir; do
[ -f "$dir/cookies.sqlite" ] && echo "$dir" && break
done)
If no Firefox profile or cookies.sqlite is found:
- Report: "Firefox cookies.sqlite not found. Is Firefox installed and has been used to log in to <domain>?"
- Return empty/error — let the calling skill handle the fallback.
Step 2: Copy Database
Firefox locks cookies.sqlite while running. Copy to a temp location:
cp "$PROFILE_DIR/cookies.sqlite" /tmp/llm-wiki-firefox-cookies.sqlite
# Also copy the WAL file if it exists (contains recent writes)
[ -f "$PROFILE_DIR/cookies.sqlite-wal" ] && \
cp "$PROFILE_DIR/cookies.sqlite-wal" /tmp/llm-wiki-firefox-cookies.sqlite-wal
Step 3: Query Cookies
Extract cookies for the requested domain:
sqlite3 /tmp/llm-wiki-firefox-cookies.sqlite \
"SELECT name, value FROM moz_cookies
WHERE host LIKE '%<domain>%'
AND expiry > strftime('%s','now')
ORDER BY name;"
The expiry > strftime('%s','now') filter skips expired cookies.
Step 4: Format Cookie Header
Build a standard Cookie: header string from the results:
Cookie: name1=value1; name2=value2; name3=value3
If the query returns zero rows:
- Report: "No cookies found for <domain>. Make sure you're logged in to <domain> in Firefox."
- Return empty — let the calling skill handle the fallback.
Step 5: Cleanup
Remove the temp copy:
rm -f /tmp/llm-wiki-firefox-cookies.sqlite /tmp/llm-wiki-firefox-cookies.sqlite-wal
Security
- Domain-scoped: Only extract cookies for the specifically requested domain — never dump all cookies.
- No logging: Never write raw cookie values to wiki pages, raw files, or commit messages.
- Temp cleanup: Always delete the temp database copy after extraction.
- Expiry-aware: Filter out expired cookies at query time.
Platform
macOS only. Firefox profile path: ~/Library/Application Support/Firefox/Profiles/.
For Linux, the path would be ~/.mozilla/firefox/ — not currently supported but straightforward to add.
Dependencies
- sqlite3 — pre-installed on macOS
- Firefox — must be installed with cookies for the target domain
Related Skills
RonanCodes/skills/worktree
development
VerifiedTrustedCommunity
--- name: worktree description: Coordinate multiple agents on one repo via a worktree-lock pool, so two agents never clobber each other's working tree. Acquire the first free slot (main, then beta/gamma… worktrees, created on demand), work there on your own branch, release when you've pushed. Use before modifying any repo that might be in use by another agent (factory, dataforce, etc.), or whenever you're told a repo is being worked on. Backed by `ro worktree`. category: development argument-hin
SKILL.mdUpdated May 25, 2026
RonanCodes/skills/ship
testing
VerifiedTrustedCommunity
--- name: ship description: Ship a feature branch the local-CI-first way — run the full local gate, push, open a PR, squash-merge, then deploy, without waiting on GitHub Actions. Use when a branch is ready for main and you want it merged and deployed now. Reads CI policy from `ro ci` (default skips remote CI because GitHub Actions billing keeps hitting limits). Sibling to /ro:gh-ship (waits on GitHub checks) and /ro:cf-ship (the deploy half). Triggers on "ship it", "ship this", "merge and deploy
SKILL.mdUpdated May 25, 2026
RonanCodes/skills/setup-logging
testing
VerifiedTrustedCommunity
--- name: setup-logging description: Set up (or audit) the observability stack in a TanStack Start + Cloudflare Workers app so it is "diagnosable by default" — structured logging (logtape) with a request context carrying trace_id + userId + tenant/orgId, a trace_id propagated FE→BE→logs→Sentry→PostHog, Cloudflare Workers observability enabled, and Sentry + PostHog wired. Two modes: `setup` (wire it into an app) and `audit` (check an existing app + report gaps). Use when scaffolding a new app, wh
SKILL.mdUpdated May 24, 2026
RonanCodes/env
development
VerifiedTrustedCommunity
Manage credentials INSIDE the active ~/.claude/.env file — read which token/account to use for a given app (Simplicity vs Dataforce vs Ronan-personal), add or update a secret WITHOUT it passing through the chat (an interactive Terminal window prompts for it), and track secrets that were exposed in a transcript so they get rotated. Sibling to /ro:context (which switches WHICH env file is active). Use when the user wants to add an API key/token/secret, asks "which credential do I use for X", needs the env organized/labelled, or a secret was pasted into the chat and should be rotated.
SKILL.mdUpdated May 24, 2026