What is rod-mcp copilot-instructions.md?

A set of coding rules and project notes for rod-mcp, a Go server that controls Chrome or Chromium through browser automation.

Use it when changing rod-mcp code, especially its browser tools, shared types, build process, tests, or generated files.

It gives coding assistants the repository context, supported checks, and boundaries they need to suggest relevant changes safely.

How aliwatters/rod-mcp configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to aliwatters/rod-mcp. 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/aliwatters/rod-mcp/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/aliwatters/rod-mcp

Made for: GitHub Copilot.

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/aliwatters/rod-mcp/copilot-instructions/github.svg)](https://agentmods.dev/instructions/aliwatters/rod-mcp/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/aliwatters/rod-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/aliwatters/rod-mcp/copilot-instructions/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/aliwatters/rod-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/aliwatters/rod-mcp/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 740 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.

Model	Per session	Once invoked
Fable 5.1	$0.00740	$0.00740
Opus 5.5	$0.00296	$0.00296
Sonnet 5.5	$0.00148	$0.00148
Haiku 4.5	$0.00074	$0.00074

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

Security

Grade A, and why

rod-mcp copilot-instructions.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 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.

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.

.github/copilot-instructions.md · 72 lines

How it starts

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

Copilot Instructions for rod-mcp

rod-mcp is a Go MCP server that wraps go-rod browser automation and exposes browser control tools over stdio. Keep suggestions focused on the public repository and avoid private paths, hostnames, credentials, incidents, support queues, or agent orchestration process details.

Repository Context

Go module: github.com/aliwatters/rod-mcp.
Runtime: follow go.mod for the supported Go version and dependency set.
MCP framework: github.com/mark3labs/mcp-go.
Browser automation: github.com/go-rod/rod controlling Chrome or Chromium.
Main entry points are main.go, cmd.go, server.go, and runner.go.
Tool implementations live in tools/; shared browser context, config, snapshots, profiles, and embedded JavaScript live in types/.

Build and Verification

Use the same commands CI relies on when relevant:

go build -o rod-mcp
go vet ./...
go test ./...
go test -tags e2e -v -timeout 300s ./e2e/

The e2e tests launch a real browser and may need Chrome or Chromium plus system libraries. For docs-only changes, prefer lightweight checks such as git diff --check.

Code Guidance

Follow the existing Go style: standard library imports first, then external packages, then internal github.com/aliwatters/rod-mcp/... packages.
Keep MCP tools in the established pattern: define an mcp.Tool, then provide a handler factory that uses rodCtx.Execute.
Let Execute manage snapshot invalidation. Do not call InvalidateSnapshot inside tool handlers.
Preserve ref continuity for tools that interact with snapshot elements by using WithSnapshot: true where the next interaction needs an updated accessibility snapshot.
Resolve elements through the existing helper paths: refs first, CSS selectors when supported, and accessible-name matching for semantic targeting.
For React-aware filling, keep using the this binding pattern expected by rod's Eval; do not pass the DOM element as a JavaScript function argument.
Wrap errors with useful context and return MCP tool errors through existing helpers such as toolErr.
Prefer table-driven tests with t.Run and focused assertions for tool schema, handler behavior, snapshots, config, and utility functions.

Read the full file on GitHub · 72 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 · 72 lines · 740 tokens per session scan A 9d0f8dfdaf8a

Subscribe to this mod's changes

rod-mcp copilot-instructions.md is an instructions file published in the GitHub repository aliwatters/rod-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 740 tokens to every session, about $0.0030 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-08-31.

rod-mcp copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rod-mcp copilot-instructions.mdaliwatters/rod-mcp	Instructions file	0	1mo ago	MIT	A	740	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	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

rod-mcp: Instructions file for GitHub Copilot