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/aliwatters/rod-mcp/copilot-instructionsgit clone --depth 1 https://github.com/aliwatters/rod-mcpWrote 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/aliwatters/rod-mcp/copilot-instructions)<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="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.00740 | $0.00740 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
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 4d 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.
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.modfor the supported Go version and dependency set. - MCP framework:
github.com/mark3labs/mcp-go. - Browser automation:
github.com/go-rod/rodcontrolling Chrome or Chromium. - Main entry points are
main.go,cmd.go,server.go, andrunner.go. - Tool implementations live in
tools/; shared browser context, config, snapshots, profiles, and embedded JavaScript live intypes/.
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 usesrodCtx.Execute. - Let
Executemanage snapshot invalidation. Do not callInvalidateSnapshotinside tool handlers. - Preserve ref continuity for tools that interact with snapshot elements by
using
WithSnapshot: truewhere 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
thisbinding pattern expected by rod'sEval; 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.Runand focused assertions for tool schema, handler behavior, snapshots, config, and utility functions.
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.
- 4d ago First seen · 72 lines · 740 tokens per session scan A 9d0f8dfdaf8a
rod-mcp copilot-instructions.md is an instructions file published in the GitHub repository aliwatters/rod-mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 740 tokens to every session, about $0.0037 per session on Opus 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.