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 instructions/nanasess/setup-chromedriver/claude-mdgit clone --depth 1 https://github.com/nanasess/setup-chromedriverWrote 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/instructions/nanasess/setup-chromedriver/claude-md)<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="Measured on agentmods" 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 | $0.00985 | $0.00985 |
| Opus 5 | $0.00492 | $0.00492 |
| Sonnet 5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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 5d 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) 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 dependenciespnpm build- Build TypeScript files (compiles src/ to lib/)pnpm package- Package the action using ncc (creates dist/index.js)pnpm format- Format code with Prettierpnpm format-check- Check code formattingpnpm 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(thenccbundle 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/fetchJsonvia typed-rest-client (curl-like retry/fail/redirect)download.ts-downloadAndExtractZipvia@actions/tool-cacheversion.ts- Chrome version detection + Chrome-for-Testing JSON resolution with fallbackunix.ts- Linux/macOS install (apt dependency setup via@actions/exec, legacy/modern split)windows.ts- Windows install (FileVersion detection, legacy/modern split)
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.
- 5d ago First seen · 81 lines · 985 tokens per session scan A 64cc7fc36777
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.0049 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 instructions, from other repositories
antigravity-testing-kit GEMINI.md
Instructions for anhtester/antigravity-testing-kit, covering gemini ai - global automation agent rules, git pull restriction rule, browser rules (mandatory), 🖥️ viewport & mode and 🔄 thứ tự debug bắt buộc (playwright mcp).
mcp-ie-migration-vrt AGENTS.md
AGENTS.md instructions for rayven122/mcp-ie-migration-vrt, covering agents.md, file map, architecture, conventions and adding a tool.
qa-use CLAUDE.md
Instructions for desplega-ai/qa-use, covering claude.md, project map and tech stack.
ClaudeCode_Playwright_Demo CLAUDE.md
Instructions for anhtester/ClaudeCode_Playwright_Demo, covering claude ai - global automation agent rules, git pull restriction rule, browser rules (mandatory), 🖥️ viewport & mode and 🔄 thứ tự debug bắt buộc.
playwright-bdd-cursor-template CLAUDE.md
Instructions for m3au/playwright-bdd-cursor-template, covering running tests, test commands, test organization, writing tests and code architecture.
vibe-testing CLAUDE.md
Claude Code instructions for AishwaryShrivastav/vibe-testing, covering vibe test — code-aware browser testing agent, what this project does, architecture, mcp tools (13) and development.