mcp-server-excel extension-development.instructions.md

Development instructions for the ExcelMcp Visual Studio Code extension. The extension installs an MCP server that lets AI assistants automate Microsoft Excel.

In plain words
What is it for?
Use it when developing the extension, recording user-visible changes with changesets, managing versions, or preparing releases.
Why use it?
It gives developers the project rules for changes, versioning, release notes, and publishing. It also explains which files control the extension and its marketplace listing.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/sbroenne/mcp-server-excel/extension-development
Clone the repo
git clone --depth 1 https://github.com/sbroenne/mcp-server-excel

Made for: GitHub Copilot.

Per session 1,427 This file is loaded in full into every session.
When invoked 1,427 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01427 $0.01427
Opus 5 $0.00714 $0.00714
Sonnet 5 $0.00285 $0.00285
Haiku 4.5 $0.00143 $0.00143

Measured 3d ago against content hash dd506240141c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

vscode-extension/.github/instructions/extension-development.instructions.md · 215 lines

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 page
  • CHANGELOG.md - Version history (marketplace changelog tab)
  • DEVELOPMENT.md - Developer guide
  • icon.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:

  1. Run npx changeset.
  2. Select the appropriate bump type.
  3. Write an end-user-facing summary.
  4. Commit the generated .changeset/<name>.md with 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:

  1. Calculates the version from the latest tag and workflow input
  2. Updates package.json version using npm version
  3. Compiles changesets into changelog and release notes
  4. Builds and packages VS Code extension
  5. Builds all other components (MCP Server, CLI, MCPB)
  6. Publishes to VS Code Marketplace and NuGet
  7. Creates unified GitHub release with all artifacts

Local Testing (Manual Version Bump)

For local testing only, use npm version commands:

Read the full file on GitHub · 215 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. 3d ago First seen · 215 lines · 1,427 tokens per session scan A dd506240141c

Subscribe to this mod's changes

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.