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/extension-developmentgit clone --depth 1 https://github.com/sbroenne/mcp-server-excelWhat 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.01427 | $0.01427 |
| Opus 5 | $0.00714 | $0.00714 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
mcp-server-excel extension-development.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 3d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VS Code Extension Development Instructions
Instructions for developing the ExcelMcp VS Code Extension
Extension Overview
The ExcelMcp VS Code Extension provides one-click installation of the ExcelMcp MCP server for Visual Studio Code, enabling AI assistants like GitHub Copilot to automate Microsoft Excel.
Key Files:
package.json- Extension manifest (metadata, dependencies, version)src/extension.ts- Extension entry point (activation, MCP registration)README.md- Marketplace description pageCHANGELOG.md- Version history (marketplace changelog tab)DEVELOPMENT.md- Developer guideicon.png- Extension icon (128x128px, displayed in marketplace)
Changelog and Changesets (CRITICAL)
Never edit the root CHANGELOG.md manually. It is generated from changeset
fragments during release.
For a user-visible extension change:
- Run
npx changeset. - Select the appropriate bump type.
- Write an end-user-facing summary.
- Commit the generated
.changeset/<name>.mdwith the pull request.
The unified release workflow compiles pending changesets into CHANGELOG.md,
updates package versions, builds every deliverable, and publishes the release.
Version Management
Automatic Version Management (Unified Release Workflow)
DO NOT manually edit package.json version - The unified release workflow handles this:
Run Release All Components with a semantic version bump or custom version:
gh workflow run release.yml -f version_bump=patch
Unified workflow automatically:
- Calculates the version from the latest tag and workflow input
- Updates
package.jsonversion usingnpm version - Compiles changesets into changelog and release notes
- Builds and packages VS Code extension
- Builds all other components (MCP Server, CLI, MCPB)
- Publishes to VS Code Marketplace and NuGet
- Creates unified GitHub release with all artifacts
Local Testing (Manual Version Bump)
For local testing only, use npm version commands:
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.
- 3d ago First seen · 215 lines · 1,427 tokens per session scan A dd506240141c
mcp-server-excel extension-development.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-excel (645 stars, last pushed 3d ago), licensed MIT. It adds 1,427 tokens to every session, about $0.0071 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
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.