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/sbroenne/mcp-server-excel/readme-managementgit clone --depth 1 https://github.com/sbroenne/mcp-server-excelWrote 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/sbroenne/mcp-server-excel/readme-management)<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-excel/readme-management"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-excel/readme-management.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.02648 | $0.02648 |
| Opus 5 | $0.01324 | $0.01324 |
| Sonnet 5 | $0.00530 | $0.00530 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
mcp-server-excel readme-management.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 5d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Management - Quick Reference
Core Entry Documents
| File | Target Lines | Audience | Purpose |
|---|---|---|---|
/README.md |
120-150 | GitHub visitors | Acquisition page, requirements, quick start, and website routing |
/src/ExcelMcp.McpServer/README.md |
80-100 | .NET devs | Concise NuGet gateway |
/src/ExcelMcp.CLI/README.md |
180-200 | CLI users | CLI installation, syntax, and workflows |
/vscode-extension/README.md |
100-120 | VS Code users | User benefits focus |
/gh-pages/docs/index.md |
180-220 | Website visitors | Website landing page and task routing |
Feature Documentation
FEATURES.md is the repository-level navigation hub. Detailed canonical feature
documentation lives in the four category files under docs/features/. Update
the appropriate category file first whenever a feature changes, then update the
hub if its navigation or tool-selection guidance also changed.
Critical Rules
Tool & Action Counts Must Match
⚠️ IMPORTANT: CLI has FEWER tools/operations than MCP Server!
ALWAYS count tools/operations BEFORE updating any README. Never use hardcoded numbers from memory.
Before updating counts, verify by counting:
- MCP Server: Count tool files (excel_batch handled via ExcelTools.cs, not separate tool file)
- CLI: Count command group folders (includes Session commands)
- Operations: Count separately for each - they differ!
Sync counts across:
- GitHub Project About: https://github.com/sbroenne/mcp-server-excel (use the GitHub CLI to update)
/README.md/src/ExcelMcp.McpServer/README.md/src/ExcelMcp.CLI/README.md/vscode-extension/README.md/gh-pages/docs/index.md/FEATURES.md
Operation Lists Must Be Complete
⚠️ IMPORTANT: Where operation lists are documented, they MUST match the actual code!
The canonical docs/features/*.md files contain the operation lists rendered on
the website. When adding/removing operations:
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.
- 5d ago First seen · 230 lines · 2,648 tokens per session scan A 87f8debf5641
mcp-server-excel readme-management.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-excel (656 stars, last pushed yesterday), licensed MIT. It adds 2,648 tokens to every session, about $0.0132 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
excel_mcp_server AGENTS.md
AGENTS.md instructions for urjeetpatel/excel_mcp_server, covering agents.md and agent documentation and test policy.
excel-mcp CLAUDE.md
Claude Code instructions for ASH1998/excel-mcp, covering claude.md, project overview, architecture, current implementation status and ✅ completed: file operations (phase 1).
apple-health-mcp AGENTS.md
Instructions for neiltron/apple-health-mcp, covering repository guidance, project, validate changes, code map and invariants.
open-sheet AGENTS.md
Instructions for lianghsun/open-sheet, covering open-sheet — repository guide, repo layout, commands, the one invariant and core pipeline.
mcp-ms-office-documents AGENTS.md
AGENTS.md instructions for ForLegalAI/mcp-ms-office-documents, covering agents.md, project overview, architecture, key conventions and filename generation.
bilig bilig-workpaper.instructions.md
Instructions for proompteng/bilig, covering bilig workpaper formula proof, first checks, required readback, command safety and references.