What is setup-chromedriver CLAUDE.md?

Repository instructions for a GitHub Action that installs ChromeDriver, the browser-control program used by automated Chrome tests, on Ubuntu, macOS, and Windows. They list its package, build, formatting, and test commands.

Developing the ChromeDriver setup action, installing its dependencies, packaging it for GitHub Actions, formatting code, and running Jest tests.

They tell the coding assistant how to build and test the action safely and how to run one test when investigating a change.

How nanasess/setup-chromedriver configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nanasess/setup-chromedriver. 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/nanasess/setup-chromedriver/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/nanasess/setup-chromedriver

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/instructions/nanasess/setup-chromedriver/claude-md/github.svg)](https://agentmods.dev/instructions/nanasess/setup-chromedriver/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/nanasess/setup-chromedriver/claude-md"><img src="https://agentmods.dev/badge/instructions/nanasess/setup-chromedriver/claude-md/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/instructions/nanasess/setup-chromedriver/claude-md"><img src="https://agentmods.dev/badge/instructions/nanasess/setup-chromedriver/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 985 This file is loaded in full into every session.

When invoked 985 The same file — it is already loaded in full.

Security scan A 1 finding. 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.00985	$0.00985
Opus 5.5	$0.00394	$0.00394
Sonnet 5.5	$0.00197	$0.00197
Haiku 4.5	$0.00098	$0.00098

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

Security

Grade A, and why

setup-chromedriver CLAUDE.md 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `http.ts` - `fetchText` / `fetchJson` via typed-rest-client (curl-like retry/fail/redirect)

CLAUDE.md · 81 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Overview

This is the setup-chromedriver GitHub Action repository that sets up ChromeDriver for use in GitHub Actions workflows. It supports Ubuntu, macOS, and Windows platforms.

Commands

This project uses pnpm (pinned via the packageManager field in package.json). Enable it with corepack enable. pnpm is chosen for supply-chain hardening: install-time build scripts are blocked by default (allowBuilds in pnpm-workspace.yaml) and freshly published versions are held back by a cooldown (minimumReleaseAge).

Build and Development

pnpm install --frozen-lockfile - Install dependencies
pnpm build - Build TypeScript files (compiles src/ to lib/)
pnpm package - Package the action using ncc (creates dist/index.js)
pnpm format - Format code with Prettier
pnpm format-check - Check code formatting
pnpm test - Run Jest tests

Running a Single Test

pnpm test path/to/test.ts
# or
pnpm jest path/to/test.ts

Architecture

The installation logic is implemented natively in TypeScript (no shell-out to setup-chromedriver.sh / .ps1). The action follows this execution flow:

Entry Point: dist/index.js (the ncc bundle of the compiled TypeScript)
Main Logic: src/setup-chromedriver.ts - reads inputs, detects the platform/arch, then calls the appropriate native installer (installOnUnix / installOnWindows)
Installer modules (src/installer/):
- http.ts - fetchText / fetchJson via typed-rest-client (curl-like retry/fail/redirect)
- download.ts - downloadAndExtractZip via @actions/tool-cache
- version.ts - Chrome version detection + Chrome-for-Testing JSON resolution with fallback
- unix.ts - Linux/macOS install (apt dependency setup via @actions/exec, legacy/modern split)
- windows.ts - Windows install (FileVersion detection, legacy/modern split)

Read the full file on GitHub · 81 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 · 81 lines · 985 tokens per session scan A 64cc7fc36777

Subscribe to this mod's changes

setup-chromedriver CLAUDE.md is an instructions file published in the GitHub repository nanasess/setup-chromedriver (126 stars, last pushed yesterday), licensed MIT. It adds 985 tokens to every session, about $0.0039 per session on Opus 5.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.

Browser automation E2E testing Testing chromedriver codeception e2e-tests github-actions selenium-webdriver

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

setup-chromedriver: Instructions file for Claude Code