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.
npx agentmods add instructions/sbroenne/mcp-server-powerpoint/code-reviewgit clone --depth 1 https://github.com/sbroenne/mcp-server-powerpointWhat 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 | $0.00558 | $0.00558 |
| Opus 5 | $0.00279 | $0.00279 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
mcp-server-powerpoint code-review.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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Code Review
Report only actionable, high-confidence defects introduced by the pull request. Prioritize correctness, data loss, resource leaks, deadlocks, broken contracts, and security. Do not request style-only changes, speculative refactors, or unrelated cleanup.
Interop and Resource Safety
- Enforce PIA-first access across Core and ComInterop. Flag new
dynamicPowerPoint access whenMicrosoft.Office.Interop.PowerPointexposes a typed member. Allow late binding only when a concise comment identifies the missing PIA surface and a real-PowerPoint test covers it. - Verify every acquired COM object is released in a
finallyblock. Cleanup must target tracked PID-plus-start-time identities, never a process name or window-title substring. - Do not treat a generic HRESULT as proof of one specific cause without another distinguishing
check. Do not add catch-all blocks inside Core commands; unexpected failures must propagate
through
batch.Executeto the MCP boundary. - Verify counters, flags, locks, and session state are restored on every exit path. A timeout or connection failure must not become an empty successful result or strand PowerPoint.
Contract and Path Completeness
- Trace action and parameter changes through the Core interface, generated service dispatch, CLI routing, MCP schema, help, skills, and both entry points. Names, types, aliases, defaults, validation, and timeout behavior must agree. Unknown values must fail rather than select a default.
- When a change adds a dependency, response field, wait, lock, or synchronization path, verify the corresponding existence guard, integrity check, return-value check, timeout, and round-trip assertion.
- If one generated, templated, or intentionally parallel artifact changes, verify its source of truth and counterparts change consistently. Flag copied logic and checks that compare generated output against the same stale fallback used to produce it.
Protocol, Tests, and User-Facing Surfaces
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.
- 2d ago First seen · 49 lines · 558 tokens per session scan A e731fb660782
mcp-server-powerpoint code-review.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-powerpoint (19 stars, last pushed 3d ago), licensed MIT. It adds 558 tokens to every session, about $0.0028 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
mcp-server-excel llm-testing-philosophy.instructions.md
Instructions for sbroenne/mcp-server-excel, covering llm testing philosophy, what are llm tests?, the golden rule, what never belongs in a test and ❌ xfail or skip markers.
mcp-server-excel readme-management.instructions.md
Instructions for sbroenne/mcp-server-excel, covering readme management - quick reference, core entry documents, feature documentation, critical rules and tool & action counts must match.
mcp-server-excel copilot-instructions.md
Instructions for sbroenne/mcp-server-excel, covering github copilot instructions - excelmcp, repository map, environment, working rules and build and validation.
mcp-server-excel development-workflow.instructions.md
Instructions for sbroenne/mcp-server-excel, covering development workflow, branch protection, development process, pr review comment workflow and retrieve inline code review comments using github cli.
mcp-server-excel extension-development.instructions.md
Instructions for sbroenne/mcp-server-excel, covering vs code extension development instructions, extension overview, changelog and changesets (critical), version management and automatic version management (unified release workflow).
mcp-server-excel excel-connection-types-guide.instructions.md
Instructions for sbroenne/mcp-server-excel, covering excel connection types - llm quick reference, critical: loadto operation limitations, connection action compatibility, decision tree: connection vs power query and recommended workflows.