vite-plugin-mcp-client-tools: Instructions file for Codex

AGENTS.md

vite-plugin-mcp-client-tools AGENTS.md is an instructions file for Codex, OpenCode from atesgoral/vite-plugin-mcp-client-tools. It costs 1,287 tokens per session, scanned A, original, MIT.

Project instructions for a Vite plugin that lets browser-based Model Context Protocol tools communicate with coding agents through a development server.

In plain words
What is it for?
They are for building the plugin, running its example Vite app, connecting an MCP client, and testing browser tools such as taking screenshots.
Why use it?
They give an agent the repository context and development steps needed to build and test the plugin correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Claude Code.

This is atesgoral/vite-plugin-mcp-client-tools's own configuration. It tells Codex and OpenCode how to work on vite-plugin-mcp-client-tools 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 vite-plugin-mcp-client-tools configures →

Reuse

Borrowing it

Nothing to install: this file belongs to atesgoral/vite-plugin-mcp-client-tools. 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/atesgoral/vite-plugin-mcp-client-tools/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/atesgoral/vite-plugin-mcp-client-tools

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 vite-plugin-mcp-client-tools AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/atesgoral/vite-plugin-mcp-client-tools/agents-md/github.svg)](https://agentmods.dev/instructions/atesgoral/vite-plugin-mcp-client-tools/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/atesgoral/vite-plugin-mcp-client-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/atesgoral/vite-plugin-mcp-client-tools/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 vite-plugin-mcp-client-tools AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/atesgoral/vite-plugin-mcp-client-tools/agents-md"><img src="https://agentmods.dev/badge/instructions/atesgoral/vite-plugin-mcp-client-tools/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,287 This file is loaded in full into every session.
When invoked 1,287 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.01287 $0.01287
Opus 5.5 $0.00515 $0.00515
Sonnet 5.5 $0.00257 $0.00257
Haiku 4.5 $0.00129 $0.00129

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

Security

Grade A, and why

vite-plugin-mcp-client-tools 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 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.

AGENTS.md · 161 lines

How it starts

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

Guide for AI Coding Agents

This document contains important context for AI coding agents working on this project.

Project Overview

This is a Vite plugin that enables browser-based MCP (Model Context Protocol) tools. Tools run in the browser and communicate with MCP clients (like Claude Code, Cursor) via the Vite dev server.

Development Workflow

Setting Up for Development

  1. Add this MCP server to your configuration - The coding agent should have access to the example app's MCP server to test tools during development:

    • Server endpoint: http://localhost:3000/mcp (when dev server is running)
    • This gives you live access to test the tools you're building
  2. Working Directory: Always work from the repository root

  3. Example App: The example/ folder contains a minimal Vite app for testing tools

Development Cycle

# 1. Build the plugin (from root)
npm run build

# 2. Start the example dev server (from root)
cd example && npm run dev

# 3. Test tools via MCP
# The tools are now available as MCP tools for the coding agent to call
# Example: mcp__example-vite-client-tools__take-screenshot

Important: HMR Limitations

Plugin code does NOT hot-reload! When you modify:

  • Tool definitions (src/tools/*.ts)
  • Plugin code (src/index.ts, src/bridge.ts)

You must:

  1. Run npm run build
  2. Restart the Vite dev server (kill and restart cd example && npm run dev)
  3. Reload the browser page at http://localhost:3000

Only then will the serialized tool component code be updated in the browser.

Testing Tools

  1. Start the dev server: cd example && npm run dev
  2. Use the MCP tools directly from your coding agent session
  3. For screenshot tool: You'll need to interact with browser modals
  4. For console tool: Check the browser console at http://localhost:3000

Architecture

Tool Structure

Beyond the standard MCP tool definition components (name, description, inputSchema, and outputSchema), each tool can have three parts:

Read the full file on GitHub · 161 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. 2mo ago First seen · 161 lines · 1,287 tokens per session scan A af183ff680b4

Subscribe to this mod's changes

vite-plugin-mcp-client-tools AGENTS.md is an instructions file published in the GitHub repository atesgoral/vite-plugin-mcp-client-tools (17 stars, last pushed 1y ago), licensed MIT. It adds 1,287 tokens to every session, about $0.0051 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-30.

Related

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).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens