What is starling AGENTS.md?

A set of instructions for software agents sharing work in the Starling browser project. It explains how to find available work, claim a task, follow its package instructions, build and test changes, and mark work complete.

Use it to select and claim an unblocked task, work directly on the project’s main branch, commit with the task identifier, run the required checks, and report completion.

It reduces conflicts between agents and makes unfinished work easy for another agent to resume.

How starling-browser/starling configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to starling-browser/starling. 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/starling-browser/starling/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/starling-browser/starling

Made for: Codex, OpenCode.

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/starling-browser/starling/agents-md/github.svg)](https://agentmods.dev/instructions/starling-browser/starling/agents-md)

Your own site

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

Per session 5,796 This file is loaded in full into every session.

When invoked 5,796 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.05796	$0.05796
Opus 5.5	$0.02318	$0.02318
Sonnet 5.5	$0.01159	$0.01159
Haiku 4.5	$0.00580	$0.00580

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

Security

Grade A, and why

starling AGENTS.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.

`curl http://localhost:8088/<name>/`. A site that renders from disk but not

AGENTS.md · 448 lines

How it starts

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

Agents — rules of engagement

This file is the first thing an implementation agent should read when opening this repo. It explains how multiple agents share work without stepping on each other, and how a single agent can stop mid-task and have a later session resume cleanly.

TL;DR

# 1. Orient
cat AGENTS.md                            # this file
less browser-plan/13_MILESTONES.md       # where we are
less tasks/INDEX.md                      # what's available

# 2. Claim something unblocked
./tasks/lib/claim.sh claim wp:M1-03-dom-core "agent-claude-<your-handle>"

# 3. Read the package file and start working on main
less tasks/M1/wp-M1-03-dom-core.md

# 4. Commit often, with the wp id in the subject:
#    "wp:M1-03 — Node hierarchy + tests"

# 5. Build + test before completing
dotnet build && dotnet test

# 6. Mark complete:
./tasks/lib/claim.sh complete wp:M1-03-dom-core

All work happens on main. This repo doesn't use a per-package branch workflow — agents commit directly to main. (If a remote with PR review is ever wired up, the optional in_review state in tasks/SCHEMA.md is available for it; today it's unused.)

If you have to stop early, leave a handoff log entry in the task file and either keep the claim (you'll resume) or release it (./tasks/lib/claim.sh release wp:…). Either way: commit so the next agent sees the state.

The contract

You can rely on	You must do
One file per work package under `tasks/M/wp-.md`	Touch only your claimed package's file (plus your code changes)
`tasks/INDEX.md` reflects the current status	Update INDEX.md when you change a status
Work happens on `main`; commits carry the wp id in the subject	Prefix commit messages with `wp:<id> —` so history is greppable
Inbound contributions require a CLA	Make sure the contributor has a CLA on file before the work lands
Dependencies are explicit in `depends_on`	Don't start a package whose deps aren't `complete`
Stale claims age out at 72 h	Add a handoff log entry every session, even if you're "still going"

Read the full file on GitHub · 448 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 · 448 lines · 5,796 tokens per session scan A 47538d393d1f

Subscribe to this mod's changes

starling AGENTS.md is an instructions file published in the GitHub repository starling-browser/starling (64 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 5,796 tokens to every session, about $0.0232 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-engine css dotnet html rendering

starling AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
starling AGENTS.mdstarling-browser/starling	Instructions file	64	4mo ago	Apache-2.0	A	5,796	Codex, OpenCode
plan-forge dapr.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	4,975	GitHub Copilot
plan-forge database.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	1,890	GitHub Copilot
plan-forge naming.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	1,453	GitHub Copilot
plan-forge caching.instructions.mdsrnichols/plan-forge	Instructions file	6	2d ago	MIT	A	733	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode

starling: Instructions file for Codex