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/mcp-server-guide.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/mcp-server-guide)<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-powerpoint/mcp-server-guide"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/mcp-server-guide/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-powerpoint/mcp-server-guide"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/mcp-server-guide.svg" alt="Reviewed on agentmods" width="80" 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.01985 | $0.01985 |
| Opus 5.5 | $0.00794 | $0.00794 |
| Sonnet 5.5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
mcp-server-powerpoint mcp-server-guide.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 20d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Development Guide
Tool methods return the MCP SDK's Task<CallToolResult>. Results include both a
text JSON block for existing clients and the same object as structured content.
Generated tools declare an output schema derived from their Core result
contracts. A cancellation token is injected by the SDK and forwarded through
the service bridge; it is never advertised as a tool argument.
LLM-Facing Content Rules
NO EMOJIS in LLM-consumed content — never use emoji characters in:
- Tool
[Description(...)]attributes and XML/// <summary>comments — the MCP SDK extracts these into the tool schema an LLM reads directly. - skill files and any future MCP prompt content.
Use plain text markers: "IMPORTANT:", "WARNING:", "NOTE:", "CRITICAL:".
DO keep emojis in user-facing content: README.md, this repo's own governance docs, and other human-read documentation — humans appreciate visual aids; LLM tool schemas do not need them and they cost tokens for no benefit.
Two Kinds of Tools: Hand-Written vs. Generated
Most of the MCP tool surface is generated, not hand-written. Before editing anything under
Tools/, know which kind you're touching:
- Hand-written (
PresentationTools.csonly): the singlepresentationMCP tool. It is action-dispatch like Excel's file tool, but stays hand-written because create/open/list/close need custom session-registry behavior and optionalpresentation_session_id. - Generated (everything else —
slide,shape,textframe,table,notes,layout,master,animation,image,media,chart,smartart,export,pagesetup,accessibility,customshow): one action-dispatch tool per[ServiceCategory]Core domain, emitted byPowerPointMcp.Generators.Mcpfrom the Core interface's[ServiceCategory]/[McpTool]attributes and XML doc comments. Never hand-write a new tool class for one of these domains — add the operation to the Core interface (with XML docs) and the generator picks it up. Interfaces that declare[McpReadOnlyActions(...)]also get a{tool}_readMCP alias containing only those actions. The original tool remains intact, and the CLI keeps its existing command surface. Seearchitecture-patterns.instructions.md's Command Pattern section for the Core-side attribute shape.
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.
- 20d ago Changed · +2 lines · +52 tokens per session 69b9d643fcde
- 26d ago Changed · +11 lines · +145 tokens per session 7a4150462dd6
- 1mo ago Changed · +7 tokens per session bf6a38c94852
- 1mo ago Changed · +2 lines · +44 tokens per session a27a3be32c2b
- 2mo ago First seen · 160 lines · 1,737 tokens per session scan A b47f4c57051f
mcp-server-powerpoint mcp-server-guide.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-powerpoint (37 stars, last pushed yesterday), licensed MIT. It adds 1,985 tokens to every session, about $0.0079 per session on Opus 5.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
mcp-server-excel copilot-instructions.md
Copilot instructions for sbroenne/mcp-server-excel: This repository contains generated plugin publication output. Before changing anything, read the repository warning.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).