mcp-server-powerpoint: Instructions file for GitHub Copilot

.github/instructions/critical-rules.instructions.md

mcp-server-powerpoint critical-rules.instructions.md is an instructions file for GitHub Copilot from sbroenne/mcp-server-powerpoint. It costs 1,486 tokens per session, scanned A, original, MIT.

A set of mandatory coding rules for PowerPointMcp, a tool that lets software control Microsoft PowerPoint. It defines how success and error results, exceptions, integration tests, and numbering must work.

In plain words
What is it for?
Use it when developing or reviewing PowerPointMcp commands, especially result handling, exception flow, real PowerPoint integration tests, test-driven development, and one-based indexes.
Why use it?
It prevents clients from mistaking failed operations for successful ones and keeps errors visible instead of silently hiding them.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is sbroenne/mcp-server-powerpoint's own configuration. It tells GitHub Copilot how to work on mcp-server-powerpoint itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-server-powerpoint configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sbroenne/mcp-server-powerpoint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sbroenne/mcp-server-powerpoint/main/.github/instructions/critical-rules.instructions.md
Clone the repo
git clone --depth 1 https://github.com/sbroenne/mcp-server-powerpoint

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-powerpoint critical-rules.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/critical-rules.svg)](https://agentmods.dev/instructions/sbroenne/mcp-server-powerpoint/critical-rules)
Your own site
<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-powerpoint/critical-rules"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/critical-rules.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,486 This file is loaded in full into every session.
When invoked 1,486 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.1 $0.01486 $0.01486
Opus 5 $0.00743 $0.00743
Sonnet 5 $0.00297 $0.00297
Haiku 4.5 $0.00149 $0.00149

Measured 6d ago against content hash b190cc8cb438, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mcp-server-powerpoint critical-rules.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 6d 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/critical-rules.instructions.md · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CRITICAL RULES - MUST FOLLOW

NON-NEGOTIABLE rules for all PowerPointMcp development

Rule 1: Success/ErrorMessage Invariant

NEVER Success = true with a non-null ErrorMessage. Set Success only in the success path; the field defaults to false (or is set explicitly false) alongside ErrorMessage on every failure path.

Why Critical: Confuses LLM callers and downstream consumers of the MCP JSON payload — a non-null error message on a "successful" result is silently ignored by most clients.

Rule 1b: No Exception Suppression in Core

NEVER wrap batch.Execute() in a try-catch that swallows the exception and returns an error result. Let exceptions propagate naturally out of Core commands — IPresentationBatch.Execute's underlying TaskCompletionSource plumbing (in PresentationBatch, ComInterop layer) already surfaces them to the caller.

The only place a catch-all belongs is the MCP tool boundary (PowerPointToolsBase.ExecuteToolAction in src/PowerPointMcp.McpServer/Tools/), which logs the HResult to stderr and serializes a structured error so the MCP host never crashes.

// CORRECT — Core: exceptions propagate
public ShapeOperationResult AddRectangle(IPresentationBatch batch, int slideIndex, ...)
{
    return batch.Execute((ctx, ct) => {
        // COM access — no try/catch here
    });
}

// WRONG — Core: swallowing and returning a fabricated error result
public ShapeOperationResult AddRectangle(IPresentationBatch batch, int slideIndex, ...)
{
    try { return batch.Execute(...); }
    catch (Exception ex) { return new ShapeOperationResult { Success = false, ErrorMessage = ex.Message }; }
}

Expected, caller-correctable failures ARE validated up front and returned as Success=false without throwing — e.g. an out-of-range slideIndex, a missing file, or an unknown sessionId. The distinction: validation failures are known preconditions checked BEFORE touching COM; unexpected COM/runtime exceptions are allowed to propagate and are only ever caught at the MCP tool boundary.

Read the full file on GitHub · 135 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. 6d ago First seen · 135 lines · 1,486 tokens per session scan A b190cc8cb438

Subscribe to this mod's changes

mcp-server-powerpoint critical-rules.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-powerpoint (19 stars, last pushed yesterday), licensed MIT. It adds 1,486 tokens to every session, about $0.0074 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens