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/mrgorrin40-tp/mcp-excel-server/agents-mdgit clone --depth 1 https://github.com/mrgorrin40-TP/mcp-excel-serverWrote 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/mrgorrin40-tp/mcp-excel-server/agents-md)<a href="https://agentmods.dev/instructions/mrgorrin40-tp/mcp-excel-server/agents-md"><img src="https://agentmods.dev/badge/instructions/mrgorrin40-tp/mcp-excel-server/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 | $0.01680 | $0.01680 |
| Opus 5 | $0.00840 | $0.00840 |
| Sonnet 5 | $0.00336 | $0.00336 |
| Haiku 4.5 | $0.00168 | $0.00168 |
Grade A, and why
mcp-excel-server 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 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Guide for AI Agents
This document provides guidance for AI agents interacting with the MCP Excel Server.
Overview
MCP Excel Server exposes Excel file manipulation capabilities through the Model Context Protocol. Use the available tools to read, write, analyze, and transform Excel files (.xlsx).
Key Principles
1. Always Use Absolute Paths
✓ CORRECT: "C:/Documents/data.xlsx"
✓ CORRECT: "/home/user/documents/data.xlsx"
✗ WRONG: "data.xlsx"
✗ WRONG: "../data.xlsx"
2. Check Before Writing
Always verify file and sheet existence before writing:
1. Call describe_workbook() to verify file exists
2. Call list_sheets() to see available worksheets
3. Then proceed with write operations
3. Use Pagination for Large Data
Never read entire large files at once:
✓ CORRECT: read_range(range="A1:J100", page_size=100)
✗ WRONG: read_range(range="A1:Z10000")
Tool Reference
Reading Tools
read_cell
Read a single cell value.
Parameters:
- file_path: str (required) - Absolute path to Excel file
- sheet_name: str (required) - Worksheet name
- cell: str (required) - Cell reference (e.g., "A1")
Returns: Cell value (string, number, or null)
read_range
Read multiple cells in a range.
Parameters:
- file_path: str (required) - Absolute path to Excel file
- sheet_name: str (required) - Worksheet name
- range: str (required) - Range notation (e.g., "A1:C10")
- page_size: int (optional) - Rows per page (default: 100)
Returns: 2D array of values
get_sheet_info
Get metadata about a worksheet.
Parameters:
- file_path: str (required) - Absolute path to Excel file
- sheet_name: str (required) - Worksheet name
Returns: Column names, types, row count, sample data
search_cells
Search for values in a worksheet.
Parameters:
- file_path: str (required) - Absolute path to Excel file
- query: str (required) - Search term
- sheet_name: str (optional) - Specific sheet or all sheets
Returns: List of matching cells with locations
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 · 254 lines · 1,680 tokens per session scan A dfb073e8ad52
mcp-excel-server AGENTS.md is an instructions file published in the GitHub repository mrgorrin40-TP/mcp-excel-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,680 tokens to every session, about $0.0084 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
fcp-sheets CLAUDE.md
Instructions for os-tack/fcp-sheets, covering fcp-sheets, project overview, architecture, key patterns and commands.
Excel-Power-Pivot-MCP CLAUDE.md
Instructions for back1ply/Excel-Power-Pivot-MCP, covering claude.md, project overview, build and test commands, build and debug build.
ExcelMCPAdvanced CLAUDE.md
Claude Code instructions for nitishkthakur/ExcelMCPAdvanced, covering excel mcp server — claude guidance, project layout, development commands, key design rules and how to use the mcp tools (for analysis tasks).
MCP_GoogleSheets CLAUDE.md
Claude Code instructions for santiagopereda/MCP_GoogleSheets, covering claude.md, project overview, key architecture concepts, mcp server structure and google sheets server implementation.
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.