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/atesgoral/vite-plugin-mcp-client-tools/agents-mdgit clone --depth 1 https://github.com/atesgoral/vite-plugin-mcp-client-toolsWrote 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/atesgoral/vite-plugin-mcp-client-tools/agents-md)<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="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.1 | $0.01287 | $0.01287 |
| Opus 5 | $0.00643 | $0.00643 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00129 | $0.00129 |
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 6d 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 — 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
-
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
- Server endpoint:
-
Working Directory: Always work from the repository root
-
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:
- Run
npm run build - Restart the Vite dev server (kill and restart
cd example && npm run dev) - Reload the browser page at
http://localhost:3000
Only then will the serialized tool component code be updated in the browser.
Testing Tools
- Start the dev server:
cd example && npm run dev - Use the MCP tools directly from your coding agent session
- For screenshot tool: You'll need to interact with browser modals
- 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:
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.
- 6d ago First seen · 161 lines · 1,287 tokens per session scan A af183ff680b4
vite-plugin-mcp-client-tools AGENTS.md is an instructions file published in the GitHub repository atesgoral/vite-plugin-mcp-client-tools (16 stars, last pushed 10mo ago), licensed MIT. It adds 1,287 tokens to every session, about $0.0064 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-30.
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).
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).
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.
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.
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.