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.
curl -O https://raw.githubusercontent.com/sbroenne/mcp-server-powerpoint/main/.github/instructions/critical-rules.instructions.mdgit clone --depth 1 https://github.com/sbroenne/mcp-server-powerpointWrote 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-powerpoint/critical-rules)<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>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.01486 | $0.01486 |
| Opus 5 | $0.00743 | $0.00743 |
| Sonnet 5 | $0.00297 | $0.00297 |
| Haiku 4.5 | $0.00149 | $0.00149 |
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.
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.
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.
- 6d ago First seen · 135 lines · 1,486 tokens per session scan A b190cc8cb438
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.
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.
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.
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).
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).
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.
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.