mcp-server-excel bug-fixing-checklist.instructions.md

mcp-server-excel bug-fixing-checklist.instructions.md is an instructions file for GitHub Copilot from sbroenne/mcp-server-excel. It costs 301 tokens per session, scanned A, original, MIT.

A bug-fixing checklist for an Excel server that connects a service, application logic, and Microsoft Excel automation. It requires finding the root cause, adding a focused regression test, fixing the responsible layer, and verifying the resulting workbook or response.

In plain words
What is it for?
Use it to trace bugs across command-line and MCP entry points, inspect related branches and generated files, add regression coverage, run focused tests, and complete repository audits.
Why use it?
It prevents fixes that hide only the visible symptom or leave the same defect in another command path.

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/bug-fixing-checklist
Clone the repo
git clone --depth 1 https://github.com/sbroenne/mcp-server-excel

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for mcp-server-excel bug-fixing-checklist.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sbroenne/mcp-server-excel/bug-fixing-checklist.svg)](https://agentmods.dev/instructions/sbroenne/mcp-server-excel/bug-fixing-checklist)
Your own site
<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-excel/bug-fixing-checklist"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-excel/bug-fixing-checklist.svg" alt="Measured on agentmods" height="20"></a>
Per session 301 This file is loaded in full into every session.
When invoked 301 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.00301 $0.00301
Opus 5 $0.00151 $0.00151
Sonnet 5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

Measured 5d ago against content hash 479b29158ffe, 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 bug-fixing-checklist.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.

.github/instructions/bug-fixing-checklist.instructions.md · 31 lines

What it actually says

Bug-fix workflow

  1. Trace the failure from the user entry point through generated routing, Service, Core, and Excel COM. State the root cause before choosing a fix.
  2. Search sibling commands, fallback/retry branches, both entry points, tests, guidance, and generated/template sources for the same pattern.
  3. Add the smallest regression test that reproduces the bug and observe it fail.
  4. Fix the root cause at the owning layer without changing unrelated behavior.
  5. Rerun the regression test, then the smallest related test group.
  6. Update only documentation, help, descriptions, or workflow hints affected by the behavior change.
  7. Run the applicable repository audit scripts and summarize the root cause, same-pattern findings, behavior change, and validation in the pull request.

There is no fixed quota for tests or documentation files. Coverage must be proportional to the defect: include the reported case, meaningful boundary or error cases, and cross-entry-point coverage where the contract crosses CLI/MCP.

Do not:

  • Fix only the visible symptom while another branch retains the same defect.
  • Assert only Success; verify the resulting workbook or response state.
  • Add broad catches, silent defaults, or retries without a bounded condition.
  • Hand-edit generated artifacts instead of their source.
  • Create a separate investigation or summary document in the repository.
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. 5d ago First seen · 31 lines · 301 tokens per session scan A 479b29158ffe

Subscribe to this mod's changes

mcp-server-excel bug-fixing-checklist.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-excel (656 stars, last pushed today), licensed MIT. It adds 301 tokens to every session, about $0.0015 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.