browser-controller: Instructions file for Codex

AGENTS.md

browser-controller AGENTS.md is an instructions file for Codex, OpenCode from compnew2006/browser-controller. It costs 679 tokens per session, scanned A, original, MIT.

Repository instructions for a browser-control project, covering its TypeScript server, Chrome extension, architecture, security, builds, and tests. A Chrome extension is software that adds features to the Chrome browser.

In plain words
What is it for?
They help maintain the MCP server, local daemon, Chrome extension, browser handlers, credentials vault, and related test and build files.
Why use it?
They give an agent project-specific rules so changes follow the existing structure and do not overlook authentication, browser permissions, secrets, or tests.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex; $skill-name invocation.

This is compnew2006/browser-controller's own configuration. It tells Codex and OpenCode how to work on browser-controller itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything browser-controller configures →

Reuse

Borrowing it

Nothing to install: this file belongs to compnew2006/browser-controller. 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/compnew2006/browser-controller/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/compnew2006/browser-controller

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.

agentmods badge for browser-controller AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/compnew2006/browser-controller/agents-md/github.svg)](https://agentmods.dev/instructions/compnew2006/browser-controller/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/compnew2006/browser-controller/agents-md"><img src="https://agentmods.dev/badge/instructions/compnew2006/browser-controller/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.

agentmods 80×15 button for browser-controller AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/compnew2006/browser-controller/agents-md"><img src="https://agentmods.dev/badge/instructions/compnew2006/browser-controller/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 679 This file is loaded in full into every session.
When invoked 679 The same file — it is already loaded in full.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00679 $0.00679
Opus 5.5 $0.00272 $0.00272
Sonnet 5.5 $0.00136 $0.00136
Haiku 4.5 $0.00068 $0.00068

Measured yesterday against content hash 8f91420e2501, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

browser-controller AGENTS.md scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

AGENTS.md · 32 lines

How it starts

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

Repository Guidelines

Project Structure

  • mcp-server/src/ holds the TypeScript MCP server, daemon/bridge, tools, and credential vault.
  • extension/ is Chrome MV3: background modules wire events; dispatch/ routes calls, lib/ holds shared state, handlers implement browser behavior.
  • tests/ has Vitest suites and Chrome mocks; scripts/ has daemon, pairing, and smoke utilities; scripts/pages/ has fixtures.
  • agent-config/, specs/, docs/, and deploy/ contain editor setup, feature designs, project/audit docs, and supervisor examples.

Architecture and Security

MCP clients connect to a local daemon that validates calls and routes them over authenticated WebSockets to the paired extension. Keep schemas under mcp-server/src/tools/, registration in register-tools.ts, and browser behavior in matching handlers. Preserve timeouts and tab ownership. Pairing grants trusted clients powerful, unsandboxed browser control. Never commit secrets/private configuration; report vulnerabilities through SECURITY.md. Vault fill never clicks Submit, though site handlers may submit on input.

Build, Test, and Development

  • npm ci installs locked dependencies (Node.js 20+); npm run dev watches TypeScript; npm run build compiles to mcp-server/dist/.
  • npm test runs Vitest; focus one with npm test -- tests/v3-mock.test.ts.
  • CI runs npm run lint, npm run typecheck, npm run build, npm run test:coverage, npm run security:audit, and npm run context:lint on Node 20 and 22.
  • npm run smoke:real-chrome requires a built server and enrolled extension; it restarts the daemon and uses the normal Chrome profile.

Style and Testing

Use ES modules, two spaces, semicolons, and nearby naming. Keep tools and handlers focused; Vitest files end in *.test.ts. Add regressions for protocol, tab ownership, timeouts, and credential redaction; prefer isolated tests. Use real-Chrome smoke checks when needed.

Spec Kit, Evidence, and Agent Workflow

Read the full file on GitHub · 32 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.

  1. yesterday First seen · 32 lines · 679 tokens per session scan A 8f91420e2501

Subscribe to this mod's changes

browser-controller AGENTS.md is an instructions file published in the GitHub repository compnew2006/browser-controller (7 stars, last pushed yesterday), licensed MIT. It adds 679 tokens to every session, about $0.0027 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-27.

Related

Other instructions, from other repositories