Record E2E Gif
lablup/backend.ai-webui
Record Playwright e2e tests as one GIF per test case (video → ffmpeg palette GIF) and return a markdown table for a PR description.
A skill your agent uses when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage…
Install Octocode Chrome Devtools
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bgauryy/octocode octocode-chrome-devtools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/octocode-chrome-devtools .claude/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .claude/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtoolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bgauryy/octocode octocode-chrome-devtools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/octocode-chrome-devtools .agents/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .agents/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bgauryy/octocode octocode-chrome-devtools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/octocode-chrome-devtools .cursor/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .cursor/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bgauryy/octocode.git --path skills/octocode-chrome-devtools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bgauryy/octocode octocode-chrome-devtools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/octocode-chrome-devtools .gemini/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .gemini/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bgauryy/octocode octocode-chrome-devtoolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/octocode-chrome-devtools .github/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .github/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bgauryy/octocode octocode-chrome-devtools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bgauryy/octocode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/octocode-chrome-devtools .opencode/skills/octocode-chrome-devtools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "octocode-chrome-devtools" agent skill from https://github.com/bgauryy/octocode/tree/main/skills/octocode-chrome-devtools into .opencode/skills/octocode-chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "octocode-chrome-devtools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
octocode-chrome-devtools- GitHub stars
- 949
- Token cost
- ~1.6k tokens
- SKILL.md length
- 611 words
- Files
- 60 (incl. scripts, references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage…
- A live page needs Chrome DevTools/CDP evidence: network failures
- SKILL.md covers Route (pick one), Scripts (node /scripts/) and References (load one at a time)
- Calls node
- DOM/CSS actionability
What it does
Octocode Chrome Devtools is an agent skill from bgauryy/octocode. 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).
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 61 other files, including scripts and reference files (for example `README.md`, `agents/openai.yaml` and `references/cdp-agent.md`).
It sits in Testing & QA, covering Browser testing and Web scraping. It works with Chrome DevTools, Model Context Protocol and GitHub. The repository describes itself as: Code research platform for AI agents; find, understand, and prove context across your code and all of GitHub, in a fraction of the tokens. One toolset, MCP or CLI. The licence is MIT.
When your agent uses it
- A live page needs Chrome DevTools/CDP evidence: network failures
- DOM/CSS actionability
- Screenshots/PDF
- Cookies/storage
Example prompts
- “/octocode-chrome-devtools”
What it can do on your machine
Read from SKILL.md and the folder at commit c265e3f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Octocode Chrome Devtools loads about 1.6k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 611 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from bgauryy/octocode at commit c265e3f, republished under its MIT licence (© bgauryy). 611 words, ~1,588 tokens.
Download SKILL.mdSave it as
.claude/skills/octocode-chrome-devtools/SKILL.md (or your agent's skills folder). This skill also uses 59 other files; get the full folder from GitHub.- name
- octocode-chrome-devtools
- description
- 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).
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) |
Show full SKILL.md (196 more words)Show less
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.
© bgauryy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 59 other files (scripts, references) in skills/octocode-chrome-devtools of bgauryy/octocode.
- SKILL.md
- README.md
- agents/openai.yaml
- references/cdp-agent.md
- references/cdp-checks.md
- references/cdp-domain-map.md
- references/chrome-flags.md
- references/cookie-bridge.md
- references/har-capture.md
- references/intents-auth.md
- references/intents-automation.md
- references/intents-debug.md
- references/intents-environment.md
- references/intents-inspect.md
- references/intents-storage.md
- references/intents.md
- references/recovery.md
- references/script-patterns-async.md
- references/script-patterns-browser.md
- … and 41 more
Open the folder on GitHubat commit c265e3f
Compare with similar skills
Octocode Chrome Devtools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Octocode Chrome Devtools this skillbgauryy/octocode | 949 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Record E2E Giflablup/backend.ai-webui | 133 | — | ~907 | Automated safety check: Notes | LGPL-3.0 | |
| Anti Detect Browserantibrow/anti-detect-browser-skills | 17 | — | ~9.8k | Automated safety check: Warn | MIT | |
| Browser Testing with Chrome DevToolsaddyosmani/agent-skills | 103k | 4 repos | ~3.5k | Automated safety check: Warn | MIT | |
| Chrome Devtoolseinverne/dotfiles | 121 | 1 repos | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Diff-Driven Smoke TestsSkyvern-AI/skyvern | 23k | — | ~5.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Anti Detect Browser
antibrow/anti-detect-browser-skills
Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone…
Browser Testing with Chrome DevTools
addyosmani/agent-skills
Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.
Chrome Devtools
einverne/dotfiles
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts.
Diff-Driven Smoke Tests
Skyvern-AI/skyvern
Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.
System Bridge Testing Workflow
timmo001/system-bridge
How to test System Bridge - Go table-driven tests and commands, web-client quality checks (lint/typecheck/format, no unit tests), the Chrome DevTools MCP interactive test loop for UI and WebSocket…
More from bgauryy/octocode
All 12 skills in this repoOctocode Benchmark Runner
bgauryy/octocode
Runs blind pairwise comparisons of Octocode against a gh-based baseline over markdown research questions, scored by total characters through the model rather than self-report.
Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
Evidence-Backed Documentation Writer
bgauryy/octocode
Writes, repairs and copyedits project docs against the Google developer documentation style guide, verifying claims in the repository before stating them.
Octocode Mannequin
bgauryy/octocode
Poses and animates a 22-bone anatomical humanoid rig with joint range-of-motion limits, using a Node CLI, a Three.js viewer and WebMCP tools an agent can drive live.
Octocode Skills Manager
bgauryy/octocode
Finds, rates, reviews, creates, improves, installs and syncs Agent Skill folders from local workspaces, registries or remote sources, with a user gate before any write.
Octocode Brainstorming
bgauryy/octocode
Walks an idea through framing, diverging into options, researching evidence and stress-testing before converging on a build, prototype, narrow or park decision.
Related
Categories
Questions about Octocode Chrome Devtools
What does Octocode Chrome Devtools do?
A skill your agent uses when a live page needs Chrome DevTools/CDP evidence: network failures, console errors, performance, DOM/CSS actionability, screenshots/PDF, cookies/storage…. Octocode Chrome Devtools is an agent skill from bgauryy/octocode. 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.
When should I use Octocode Chrome Devtools?
Octocode Chrome Devtools fits situations like: A live page needs Chrome DevTools/CDP evidence: network failures; DOM/CSS actionability; screenshots/PDF; cookies/storage.
How do I install Octocode Chrome Devtools in Claude Code?
Run `npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a claude-code`. Or copy the skill folder (skills/octocode-chrome-devtools in bgauryy/octocode) into .claude/skills/octocode-chrome-devtools in your project. Claude Code loads it when a task matches its description.
How do I install Octocode Chrome Devtools in Codex?
Run `npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a codex`. Or copy the skill folder (skills/octocode-chrome-devtools in bgauryy/octocode) into .agents/skills/octocode-chrome-devtools in your project. Codex loads it when a task matches its description.
Can I use Octocode Chrome Devtools in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bgauryy/octocode --skill octocode-chrome-devtools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/octocode-chrome-devtools, .gemini/skills/octocode-chrome-devtools, .github/skills/octocode-chrome-devtools and .opencode/skills/octocode-chrome-devtools in your project.
What does Octocode Chrome Devtools need to run?
Going by SKILL.md and its folder, Octocode Chrome Devtools needs the command-line tools its instructions call (node).
Does Octocode Chrome Devtools access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Octocode Chrome Devtools safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Octocode Chrome Devtools use?
Octocode Chrome Devtools is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Octocode Chrome Devtools use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.2k tokens, read only when the agent opens those files.
What are the alternatives to Octocode Chrome Devtools?
Skills that share tags, products or a category with Octocode Chrome Devtools: Record E2E Gif (lablup/backend.ai-webui, 133 stars), Anti Detect Browser (antibrow/anti-detect-browser-skills, 17 stars), Browser Testing with Chrome DevTools (addyosmani/agent-skills, 103k stars) and Chrome Devtools (einverne/dotfiles, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Octocode Chrome Devtools?
bgauryy (a GitHub user) maintains it in bgauryy/octocode, which has 949 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 9, 2026.
Source: bgauryy/octocode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.