Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/cleanup-chrome/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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.
[](https://agentmods.dev/skills/rakovi4/continue-framework/cleanup-chrome)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/cleanup-chrome"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/cleanup-chrome/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.
<a href="https://agentmods.dev/skills/rakovi4/continue-framework/cleanup-chrome"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/cleanup-chrome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00071 | $0.00416 |
| Opus 5.5 | $0.00028 | $0.00166 |
| Sonnet 5.5 | $0.00014 | $0.00083 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade C, and why
cleanup-chrome scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf acceptance/build/test-results/frontendTest/binary 2>/dev/null What it actually says
Clean Up Orphaned Chrome Processes
Failed or interrupted Selenium test runs leave behind chromedriver and headless Chrome processes. These accumulate and exhaust system resources, causing new Selenium tests to fail with Connection reset / TimeoutException on the Chrome DevTools WebSocket.
Action
-
Count orphaned processes to assess the situation:
echo "chromedriver: $(tasklist //FI "IMAGENAME eq chromedriver.exe" 2>/dev/null | grep -c chromedriver)" && echo "chrome: $(tasklist //FI "IMAGENAME eq chrome.exe" 2>/dev/null | grep -c chrome)" -
Kill all chromedriver processes (these are always test-spawned):
taskkill //IM chromedriver.exe //F 2>&1 | tail -1 -
Kill all headless Chrome processes:
taskkill //IM chrome.exe //F 2>&1 | tail -1 -
Repeat kill commands until counts reach 0 — processes can respawn briefly as child processes exit. Usually 2-3 rounds suffice.
-
Clean locked test output if it exists:
rm -rf acceptance/build/test-results/frontendTest/binary 2>/dev/null
Output
Report how many processes were killed and confirm cleanup is complete.
Note
This kills ALL Chrome and chromedriver processes, including the user's own browser. Warn the user before proceeding if they might have a Chrome browser open with unsaved work.
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 · 41 lines · 71 tokens per session scan C 3d3f29ecc01a
cleanup-chrome is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 71 tokens to every session and 416 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…