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/development-workflow.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/development-workflow)<a href="https://agentmods.dev/instructions/sbroenne/mcp-server-powerpoint/development-workflow"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/development-workflow/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/development-workflow"><img src="https://agentmods.dev/badge/instructions/sbroenne/mcp-server-powerpoint/development-workflow.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.00394 | $0.00394 |
| Opus 5.5 | $0.00158 | $0.00158 |
| Sonnet 5.5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
mcp-server-powerpoint development-workflow.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.
What it actually says
Build and release constraints
- Keep SDK setup compatible with
global.json; preserve warnings-as-errors and analyzers. Use existing CI and pre-commit checks, not substitute scripts. ci.ymlruns without PowerPoint. Real-COM tests stay local on Windows with desktop PowerPoint. Do not remove that coverage or pretend a build covers COM.- Preserve pre-commit selection of docs-only, tooling, and runtime changes.
MCP tests marked
RequiresPowerPoint=trueneed PowerPoint even though most MCP protocol tests do not. - Local builds call
scripts/Stop-PowerPointMcpProcesses.ps1. Preserve tracked PID-plus-start-time ownership. In shared environments, use-p:PowerPointMcpSkipCleanup=trueto avoid build-triggered cleanup; this is not permission to bypass hooks or disable test cleanup. release.ymlowns versions, changelog generation, and publication. Never dispatch it as a test.- Skills are concise entry points in
skills/; detailed guidance is maintained on the documentation site.scripts/Build-AgentSkills.ps1packages the skills, whilescripts/Build-Plugins.ps1copies the relevant skills into plugins. Seeskills/README.md; a solution build does not package skills.
Procedures: release strategy, plugin publication, and agent setup. Hook setup and check selection: development guide.
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 · +1 lines · +21 tokens per session d0d23e0bb4c2
- 1mo ago First seen · 29 lines · 373 tokens per session scan A 815b52443b59
mcp-server-powerpoint development-workflow.instructions.md is an instructions file published in the GitHub repository sbroenne/mcp-server-powerpoint (37 stars, last pushed yesterday), licensed MIT. It adds 394 tokens to every session, about $0.0016 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-09-12.
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).