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.
npx agentmods add skills/encod3d-sec/torch/chrome-devtools-browsernpx skills add Encod3d-Sec/TORCH --skill chrome-devtools-browsergit clone --depth 1 https://github.com/Encod3d-Sec/TORCHWhat 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 | $0.00162 | $0.01254 |
| Opus 5 | $0.00081 | $0.00627 |
| Sonnet 5 | $0.00032 | $0.00251 |
| Haiku 4.5 | $0.00016 | $0.00125 |
Grade A, and why
chrome-devtools-browser 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 3d 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.
| **The real API calls the app makes** | `list_network_requests` (add `includePreservedRequests:true` to span the login redirects); this is the authenticated API map a curl crawl never sees | How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chrome-devtools-browser
Headless browser.sh cannot solve a human login. This skill brings up a visible chromium on the
Kali desktop (:0) the operator can click and type into, with its DevTools port tunnelled back so the
chrome-devtools MCP drives and watches it. Two roles at once: the human authenticates; the agent
observes + acts. The VM holds the VPN/egress path, so it reaches both internet and in-scope targets.
1. Bring it up (one command)
bash scripts/browser-visible.sh <login-url> --profile bbtest-<eng>
# e.g. bash scripts/browser-visible.sh https://target.example/ib --profile bbtest-<eng>
It resolves the VM's seat session, unlocks/wakes :0, frees the CDP port, launches chromium as the
seat user on :0 in a named tmux session (a dedicated per-engagement profile, so the operator's own
profile/cookies stay clean), then reuses scripts/browser.sh to forward CDP to http://127.0.0.1:9222.
It prints VISIBLE on :0 when a real on-screen window exists (not merely a listening port). If it prints
a no (:N) desktop session message, the VM has no desktop - fall back to scripts/browser.sh (headless).
2. Attach + hand off for login
- The chrome-devtools MCP attaches to
http://127.0.0.1:9222. Confirm withlist_pages;navigate_pageto the login URL if needed. - Stay off the browser while the operator enters credentials. Take a
take_screenshotso they can confirm the page, then wait for their "logged in" before you drive again. The operator owns credential entry and the phone approval; the agent never types a personal code / PIN.
3. Drive + observe (chrome-devtools MCP capability map)
| Need | MCP tool |
|---|---|
| List/select tabs | list_pages (select the target tab; ignore the operator's other tabs) |
| Go to a page / back / reload | navigate_page |
| Rendered DOM (elements + uids) | take_snapshot |
| Visual PoC / confirm state | take_screenshot -> a web evidence image (hand to Skill(screenshot)/Skill(evidence)) |
| The real API calls the app makes | list_network_requests (add includePreservedRequests:true to span the login redirects); this is the authenticated API map a curl crawl never sees |
| One request's headers/body/cookies | get_network_request <reqid> |
| Console / JS errors | list_console_messages |
| Read client config / globals, confirm DOM-XSS | evaluate_script (e.g. __NEXT_DATA__, window.*, fire a payload in the real DOM) |
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.
- 3d ago First seen · 76 lines · 162 tokens per session scan A 062f979560ce
chrome-devtools-browser is a skill published in the GitHub repository Encod3d-Sec/TORCH (282 stars, last pushed 5d ago), licensed MIT. It adds 162 tokens to every session and 1,254 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.