What is client-debug?

A development tool for collecting diagnostics from a running web app, including on a phone or installed progressive web app (PWA).

Use it to check mobile safe areas, viewport behavior, connection status, app state, performance, and which build is running.

It helps investigate layout and performance problems that are difficult to inspect when normal browser developer tools are unavailable.

How G-Research/bobbit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to G-Research/bobbit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/G-Research/bobbit/main/.claude/skills/client-debug/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/G-Research/bobbit

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/g-research/bobbit/client-debug/github.svg)](https://agentmods.dev/skills/g-research/bobbit/client-debug)

Your own site

<a href="https://agentmods.dev/skills/g-research/bobbit/client-debug"><img src="https://agentmods.dev/badge/skills/g-research/bobbit/client-debug/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/g-research/bobbit/client-debug"><img src="https://agentmods.dev/badge/skills/g-research/bobbit/client-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,776 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.01776
Opus 5.5	$0.00015	$0.00710
Sonnet 5.5	$0.00007	$0.00355
Haiku 4.5	$0.00004	$0.00178

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

Security

Grade A, and why

client-debug scanned grade A with 0 findings 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/client-debug/SKILL.md · 122 lines

How it starts

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

Client debug & mobile/PWA layout playbook

Use this when you need information back from the running web client but can't get it the usual way — most often an installed mobile PWA (iOS "Add to Home Screen"), where there is no DevTools console and things like env(safe-area-inset-*), the iOS viewport "lie", connection state, or which build is actually live can only be observed on the real device.

The tool: Client debug

A flag-gated diagnostic lives in src/app/client-debug.ts.

Enable it: Settings → the Debug toggle next to Restart Server in the footer. It's the unified dev switch (it flips the bobbit-client-debug localStorage flag AND arms boot-timing perf). Dev-harness only — it's gated on the server's harness status (harnessRestartAvailable), so it appears whenever the gateway runs under the dev harness, including on a phone pointed at that dev gateway (which is the whole point); it's hidden on production gateways.
Use it: a small floating DBG button appears in the chat view (desktop and mobile). Tapping it dumps a fenced, copy-pasteable report into the message composer so the user can read it or send it to you.
Report sections: Environment (incl. build= id), Viewport / layout, Performance, plus any registered via registerDebugSection(name, fn) (e.g. App state, wired from render.ts). Add new sections there or via the registry — keep client-debug.ts generic, not bug-specific.
Build id: the DBG button shows a short build id and the report's Environment section prints build=…. Use it to confirm the device is running the build you just shipped (the #1 gotcha when iterating on a hard-to- reload installed PWA).

Getting a dump from the user: ask them to enable the flag, tap DBG, and send the message. On desktop you can instead run collectClientDebug() logic mentally from browser_eval, but the button is the mobile-friendly path.

Version/identity: the report includes buildId (via the boot waterfall when present) and live viewport numbers. If you change client code while iterating, have the user confirm the change took effect by re-dumping — the network-first service worker means a cold relaunch (while online) pulls the latest; no reinstall needed.

Read the full file on GitHub · 122 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.

2mo ago First seen · 122 lines · 37 tokens per session scan A f9da3ac8eddc

Subscribe to this mod's changes

client-debug is a skill published in the GitHub repository G-Research/bobbit (18 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,776 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging Mobile

client-debug next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
client-debugG-Research/bobbit	Skill	18	1mo ago	MIT	A	37	Claude Code
ios-fixgarrytan/gstack	Skill	140k	yesterday	MIT	A	15	Claude Code
node-connectopenclaw/openclaw	Skill	394k	yesterday	MIT	A	39	Claude Code, Codex
google-mobile-ads-validategoogle/skills	Skill	22k	yesterday	Apache-2.0	A	84	Claude Code, Codex
jetpack-compose-performanceandroid/skills	Skill	10k	yesterday	Apache-2.0	A	41	Claude Code
android-tombstone-symbolicationdotnet/skills	Skill	5.8k	yesterday	MIT	A	176	Claude Code
swiftui-performance-auditsteipete/agent-scripts	Skill	7.5k	7d ago	MIT	A	24	Claude Code, Codex

bobbit: Skill for Claude Code