cookie-debugging

cookie-debugging is a skill for Claude Code from operasoftware/opera-devtools-mcp. It costs 71 tokens per session (2,175 once invoked), scanned A, a copy of cookie-debugging, Apache-2.0.

A browser debugging tool that uses Chrome DevTools to inspect cookies, login sessions, and related browser state. Cookies are small pieces of browser data that websites use to remember users and their permissions.

In plain words
What is it for?
It is for checking Cookie and Set-Cookie headers, testing cookie consent banners, and investigating authentication and session problems.
Why use it?
It helps explain failed logins, 401 or 403 errors, redirects, expired sessions, and incorrect cookie settings without guessing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the opera-devtools-mcp plugin — 8 skills shipped together

Good fit It is for checking Cookie and Set-Cookie headers, testing cookie consent banners, and investigating authentication and session problems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/operasoftware/opera-devtools-mcp/cookie-debugging
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add operasoftware/opera-devtools-mcp --skill cookie-debugging
Clone the repo
git clone --depth 1 https://github.com/operasoftware/opera-devtools-mcp

Made for: Claude Code.

Or install opera-devtools-mcp, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cookie-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/operasoftware/opera-devtools-mcp/cookie-debugging/github.svg)](https://agentmods.dev/skills/operasoftware/opera-devtools-mcp/cookie-debugging)
Your own site
<a href="https://agentmods.dev/skills/operasoftware/opera-devtools-mcp/cookie-debugging"><img src="https://agentmods.dev/badge/skills/operasoftware/opera-devtools-mcp/cookie-debugging/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cookie-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/operasoftware/opera-devtools-mcp/cookie-debugging"><img src="https://agentmods.dev/badge/skills/operasoftware/opera-devtools-mcp/cookie-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.02175
Opus 5.5 $0.00028 $0.00870
Sonnet 5.5 $0.00014 $0.00435
Haiku 4.5 $0.00007 $0.00217

Measured 1mo ago against content hash eeb526491ce5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cookie-debugging scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Call `evaluate_script` with `() => fetch(window.location.href)`
Origin

This is a copy

100% identical to cookie-debugging — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/cookie-debugging/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Core Concepts

HttpOnly vs Client-Side Storage

Cookies marked HttpOnly cannot be accessed or modified by client-side JavaScript (cookieStore or document.cookie). However, the browser automatically attaches active HttpOnly cookies to outgoing HTTP request headers (Cookie).

  • To inspect current HttpOnly values: Look at the Cookie request header of any outgoing HTTP request via get_network_request.
  • To inspect how cookies were created or configured: Look at the Set-Cookie response header of login/auth responses.
  • To inspect non-HttpOnly cookies: Use evaluate_script with the modern cookieStore API (async () => await cookieStore.getAll()).

Session Strategy: Live Tab vs Isolated Context

Choose the right session environment to avoid state contamination (e.g., residual analytics or auth tokens):

Strategy When to Use Setup / Teardown
Live Tab (Active Page) Diagnosing an active user session, live 401/403 error, or current state. Operates directly on the currently selected page.
Clean-Slate (isolatedContext) Testing cookie consent banners, first-time visits, or zero-cookie guarantees. Call new_page with a unique isolatedContext (e.g. "consent-audit-1"). When finished, call close_page.

Client-Side Capabilities & Limitations

Action Client JavaScript (cookieStore / document.cookie) DevTools Network & Context Tools
Read Non-HttpOnly ✅ async () => await cookieStore.getAll() ✅ get_network_request (Request Cookie)
Read HttpOnly ❌ Blocked by browser security ✅ get_network_request (Request Cookie)
Inspect Attributes (Domain, Path, SameSite, Expires) ✅ async () => await cookieStore.getAll() ✅ get_network_request (Response Set-Cookie)
Modify / Delete Non-HttpOnly ✅ async () => await cookieStore.set(...) N/A
Modify / Delete HttpOnly ❌ Silent failure in JavaScript ✅ Use new_page(isolatedContext: ...) for clean state

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 150 lines · 71 tokens per session scan A eeb526491ce5

Subscribe to this mod's changes

cookie-debugging is a skill published in the GitHub repository operasoftware/opera-devtools-mcp (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 2,175 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to cookie-debugging, differing in 13 lines, and is treated as a copy.

Related

Other skills, from other repositories

chrome-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.

ChromeDevTools/chrome-devtools-mcp · 31 tokens

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

ChromeDevTools/chrome-devtools-mcp · 50 tokens

chrome-devtools

Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).

ChromeDevTools/chrome-devtools-mcp · 55 tokens

opencli-autofix

Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.

jackwener/OpenCLI · 61 tokens

chrome-performance-optimizer

Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…

chromium/chromium · 119 tokens

nullaway

Guide for resolving NullAway static analysis errors. Best practices for: Passing ObservableSupplier/Supplier Dereferencing potentially @Nullable values Adding @NullMarked to Java code.

chromium/chromium · 43 tokens