mcp-server-ppt: Instructions file for GitHub Copilot

.github/instructions/development-workflow.instructions.md

mcp-server-ppt development-workflow.instructions.md is an instructions file for GitHub Copilot from trsdn/mcp-server-ppt. It costs 1,165 tokens per session, scanned A, original, from a forked repository, MIT.

A contribution workflow for the PowerPoint MCP server, including branches, pull requests, automated checks, and review comments. A pull request is a proposed code change submitted for review before merging.

In plain words
What is it for?
Use it when starting a feature branch, opening a pull request, checking automated reviews, or preparing a release-related change.
Why use it?
It clarifies the project’s required process and reduces mistakes such as changing the protected main branch or overlooking review feedback.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is trsdn/mcp-server-ppt's own configuration. It tells GitHub Copilot how to work on mcp-server-ppt 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-ppt configures →

Reuse

Borrowing it

Nothing to install: this file belongs to trsdn/mcp-server-ppt. 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/trsdn/mcp-server-ppt/main/.github/instructions/development-workflow.instructions.md
Clone the repo
git clone --depth 1 https://github.com/trsdn/mcp-server-ppt

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-ppt development-workflow.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/development-workflow/github.svg)](https://agentmods.dev/instructions/trsdn/mcp-server-ppt/development-workflow)
Your own site
<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/development-workflow"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/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.

agentmods 80×15 button for mcp-server-ppt development-workflow.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/development-workflow"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/development-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,165 This file is loaded in full into every session.
When invoked 1,165 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin fork From a forked repository.
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.01165 $0.01165
Opus 5.5 $0.00466 $0.00466
Sonnet 5.5 $0.00233 $0.00233
Haiku 4.5 $0.00117 $0.00117

Measured 1mo ago against content hash ddc635cd6d72, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-server-ppt 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 1mo 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/development-workflow.instructions.md · 117 lines

How it starts

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

Development Workflow

Required process for all contributions

Branch Protection

⛔ NEVER commit directly to main

Enforced: PR reviews, CI/CD checks, create a branch first, up-to-date branches, no force pushes

Development Process

  1. Create feature branch: git checkout -b feature/name
  2. Standards: Zero warnings, tests pass, docs updated, security rules followed
  3. PR Checklist: Build passes, tests pass, docs updated, patterns followed
  4. Check PR review comments: After creating PR, retrieve automated review feedback and fix all issues
  5. Versions: Automated via release workflow - don't update manually

PR Review Comment Workflow

After creating a PR, ALWAYS check for automated review comments:

# Retrieve inline code review comments using GitHub CLI
# ⚠️ IMPORTANT: gh CLI requires authentication with a PERSONAL GitHub account.
# Enterprise Managed User (EMU) accounts cannot access public repos via gh CLI.
# Use: gh auth login --with-token (with a personal access token)
gh api repos/trsdn/mcp-server-ppt/pulls/PULL_NUMBER/comments --paginate

# Or use the mcp_github tool if available
mcp_github_github_pull_request_read(method="get_review_comments", owner="trsdn", repo="mcp-server-ppt", pullNumber=PULL_NUMBER)

Common automated reviewers:

  • Copilot (code quality, performance, style)
  • github-advanced-security (security scanning, code analysis)

Common issues to fix:

  • Improper /// <inheritdoc/> on constructors/test methods that don't override
  • .AsSpan().ToString() inefficiency - use [..n] range operator instead
  • Nullable type access without null checks
  • foreach → .Select() for functional style
  • Nested if statements that can be combined
  • Generic catch clauses - use specific exceptions or add justification
  • Path.Combine security warnings - suppress with justification for test code

Fix all automated review comments before requesting human review.

Test Execution

See testing-strategy.instructions.md for complete test commands.

Read the full file on GitHub · 117 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. 1mo ago Changed · +3 lines · +83 tokens per session ddc635cd6d72
  2. 1mo ago First seen · 114 lines · 1,082 tokens per session scan A 6b055e013130

Subscribe to this mod's changes

mcp-server-ppt development-workflow.instructions.md is an instructions file published in the GitHub repository trsdn/mcp-server-ppt (41 stars, last pushed yesterday), licensed MIT. It adds 1,165 tokens to every session, about $0.0047 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.

Related

Other instructions, from other repositories

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 · 9,649 tokens

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,549 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens