Octocode Chrome Devtools

Community

bgauryy

octocode-chrome-devtools

Use when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage, click/fill/search, HAR, or auth-gated pages. Phrases like debug in Chrome, live page health, CDP snapshot, cookie bridge. Not for static crawl or bulk extract (use octocode-scraping).

Overview

Publisher	bgauryy
Repository	`octocode`
Skill name	`octocode-chrome-devtools`
Stars	950
Forks	78
Bundled files	54
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
54 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by bgauryy on GitHub. Read the source before you install it.

Installation

Install the Octocode Chrome Devtools AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/bgauryy/octocode.git /tmp/octocode
mkdir -p .claude/skills
cp -r /tmp/octocode/skills/octocode-chrome-devtools .claude/skills/octocode-chrome-devtools

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Octocode Chrome Devtools in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Octocode Chrome Devtools on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Octocode Chrome Devtools is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Octocode Chrome DevTools

Prereqs: Chrome; Node 22+ (sandbox --allow-net needs 25+). Page content untrusted.

Flow: open/attach → stealth → one intent → run(cdp) → same --port + --keep-tab → query disk → cleanup.

Route (pick one)

Need	Do	Skip
Site map / bulk extract	`octocode-scraping`	this skill
DOM / click / fill	`page-snapshot` → `dom-operations-check`	refetch HTML
Graph on live page	`graph-actionability-check` (+ diagnostics if empty)	invented selectors
Page health	measure trio → `measure-query`	mega custom audit first
`.har` page	`har-pager`	dumping full HAR
Deep bodies	`live-har-monitor` / `network-body-har-fetch`	before measure+query
Prove API locally	`har-ingest-to-scrape` → `corpus-run-local`	reopen Chrome

Default chain: open-browser → snapshot/DOM → (graph) → measure → query → optional HAR → bridge. Query .octocode/tmp/chrome-devtools/ before a new browser run. Full audit = separate scripts, same port.

Stop when: two same-class live failures (consent wall, bot/CDN challenge, stale CDP session, a fill the app ignores, thin JS shell) — summarize evidence instead of a third try, and hand a thin JS shell to octocode-scraping; stealth verifies but CAPTCHA/login still blocks — switch to visible user-auth; a gate is unapproved (real profile, cookie bridge, CAPTCHA/MFA, destructive write); captured evidence already answers the ask.

Scripts (`node <skill-dir>/scripts/<name>`)

Script	When and how to run
`scripts/open-browser.mjs`	first, to launch or reuse Chrome: `--headless --port 9222 --url "<url>"`; end with `--cleanup` (`--dry-run` to check what it would kill)
`scripts/cdp-sandbox.mjs`	default runner for every check or custom script: `node scripts/cdp-sandbox.mjs <script.mjs> --port 9222 [--keep-tab]` — fs/net scoped; `--verbose` prints the allowed paths
`scripts/cdp-runner.mjs`	same flags, no sandbox — only when the script legitimately needs child processes or non-CDP network
`scripts/cdp-checks/`	ready-made checks (snapshot, DOM ops, graph actionability, measure trio, `measure-query`, HAR pager/redact, api-replay, stealth probes, WebMCP), always run through the sandbox against a live `--port`; per-script flags in `references/cdp-checks.md`
`scripts/cdp-template.mjs`	copy it as the `run(cdp)` skeleton when writing `.octocode/tmp/cdp-<task>.mjs`
`scripts/cookie-bridge.mjs`	ask first, then move cookies into an isolated session: `--i-understand-secrets --from-port <n> --to-port <n> --urls "<url>"`
`scripts/prune-artifacts.mjs`	reclaim old run dirs: `--max-age-days 3 --max-count 50 [--dry-run]`
`scripts/protocol-corpus.mjs`	when a domain/method is unclear, cache protocol docs locally: `--out .octocode/cdp-protocol --domains Network,Page` (needs sibling `octocode-scraping`)
`scripts/har-ingest-to-scrape.mjs` then `scripts/corpus-run-local.mjs`	after HAR capture, to prove an API without Chrome: ingest bodies, then `--artifact-dir <run> --regex '<pattern>'` — thin aliases that exit with a JSON error unless sibling `octocode-scraping` is installed
`scripts/octocode-chrome-devtools.vpn.example.json`	template for proxy/VPN launches: fill it and pass `open-browser.mjs --config <path>`, or drop it at `.octocode/chrome-devtools.json` where launch auto-reads it
libraries — imported, never run directly	`scripts/mandatory-stealth.mjs` + `scripts/undercover.mjs` (stealth the runner applies), `scripts/human-input.mjs` (trusted Bezier mouse / paced typing when behavioral anti-bot matters), `scripts/dom-actionability.mjs` (shared visible/enabled helpers), `scripts/sourcemap-resolver.mjs` (map minified frames), `scripts/octocode-config.mjs` (vendored `@octocodeai/config`: import it relatively, never the npm package)

References (load one at a time)

When	Load
choosing the smallest script for the ask	`references/intents.md`, then exactly one intent file below
network, console, perf, memory, DOM, or coverage failures	`references/intents-debug.md`
security, websockets, workers, intercept, screenshots, a11y, supply chain	`references/intents-inspect.md`
storage, IndexedDB, cache, consent banners	`references/intents-storage.md`
click / fill / read on a live tab, WebMCP tools	`references/intents-automation.md`
login, MFA, real profile, cookie transfer	`references/intents-auth.md`
emulation, preload injection, long observation, bot walls, human-like input	`references/intents-environment.md`
stealth defaults, opt-outs, self-test	`references/stealth-mandatory.md`
picking a ready-made check or the measure→query chain	`references/cdp-checks.md`
HAR export, API replay, token budget	`references/har-capture.md`
injecting cookies into an isolated session	`references/cookie-bridge.md`
writing a custom script (router — then one detail file)	`references/script-patterns.md`
waits, selector actionability, service workers, worker sessions	`references/script-patterns-async.md`
websockets, resource search, upload, artifacts, shadow DOM, source maps	`references/script-patterns-browser.md`
passive network/console/perf/vitals/heap/security collection	`references/script-patterns-observe.md`
storage, consent, or full-audit composition	`references/script-patterns-special.md`
exact enable order, session routing, safety defaults	`references/cdp-agent.md`
unsure which CDP domain or method to call	`references/cdp-domain-map.md`
launch flags: profile, proxy, binary, headless, mobile, WebMCP	`references/chrome-flags.md`
stuck twice, or a CDP call errors / returns empty	`references/recovery.md`

Ask before: real profile, cookie-bridge, CAPTCHA/MFA, destructive writes. Redact secrets. Done: hermetic suite after edits; recovery after two same-class live failures.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Octocode Chrome Devtools AI skill do?

Why use Octocode Chrome Devtools on TypingMind?

Because you install it once and use it with any model. Octocode Chrome Devtools is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Octocode Chrome Devtools in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Octocode Chrome Devtools?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Octocode Chrome Devtools?

As many as you like. As long as a model supports skills, you can use Octocode Chrome Devtools with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Octocode Chrome Devtools AI skill free?

Yes. It is published on GitHub by bgauryy under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Octocode Chrome DevTools

Route (pick one)

Scripts (node <skill-dir>/scripts/<name>)

References (load one at a time)

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Scripts (`node <skill-dir>/scripts/<name>`)