Report · marked 9 Oct 2026

SeleniumHQ/selenium

Solid foundations, held back in a few specific places.

Java · 34,522 stars · 5,338 files · branch trunk

78 /100 A-

Instructions 21/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 18/20Whether an agent can install the project and get it running without a human. Losing marks on environment config.Verification loop 19/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on lint and format rules.Context economy 9/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

File sizes fit in context

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

Instruction quality

Worth fixing: it never states a build, test, or run command; has no code blocks.

Repository weight

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

The full marking

Every deduction below names the file or setting it came from.

Instructions 21/27 A-

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md, Copilot instructions

✗Instruction quality 6/12

Real instructions, with gaps.

Worth fixing: it never states a build, test, or run command; has no code blocks.

5,364 characters, a workable length

uses headings, so an agent can skim it

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 18/20 A

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6

pnpm-lock.yaml pins the dependency tree.

Found pnpm-lock.yaml

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

scripts/ directory

✗Environment config 2/4

Env vars are mentioned in the README but there's no example file to copy.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

Found .nvmrc

✓Reproducible environment 2/2

.devcontainer/devcontainer.json gives a known-good environment.

Verification loop 19/22 A

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8

1403 test files against 3845 source files.

e.g. common/src/web/cn-test.html, dotnet/test/README.md, dotnet/test/remote/AssemblyTeardown.cs

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✓Continuous integration 4/4

38 GitHub Actions workflows define what "passing" means.

✗Lint and format rules 0/3

No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.

A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.

–Static type checking n/a

Not applicable — the Java compiler type checks every build.

Context economy 9/20 C

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 167 patterns.

✗File sizes fit in context 0/6

8 source files are over 100KB.

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

cpp/iedriver/Generated/atoms.h — 931KB

third_party/cpp/civetweb/civetweb.c — 527KB

third_party/js/qunit/qunit.js — 268KB

✗Repository weight 0/5

About 2401MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for SeleniumHQ/selenium

# AGENTS.md

A browser automation framework and ecosystem.

## Setup

```
pnpm install
```

## Commands

```
# TODO: nothing declares a build or test command, so an agent has to guess.
# This is the single most valuable section of this file. Fill it in.
```

## Layout

- `java/`        1525 source files
- `dotnet/`      706 source files
- `javascript/`  356 source files
- `rb/`          351 source files
- `py/`          288 source files
- `third_party/` 269 source files

## Conventions

- Tests live alongside the code they cover, following `common/src/web/cn-test.html`.
- CI defines what passing means. See `.github/workflows/bazel.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `cpp/iedriver/Generated/atoms.h` is 931KB. It will not fit comfortably in context, so read it in parts.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/SeleniumHQ/selenium.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Java AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/SeleniumHQ/selenium.svg)](https://agentreadme.com/SeleniumHQ/selenium)

Other Java repositories, marked

krahets/hello-algo 38 D iluwatar/java-design-patterns 59 B- macrozheng/mall 29 F NationalSecurityAgency/ghidra 34 D spring-projects/spring-boot 42 C doocs/advanced-java 54 C+

All Java repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in