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.
curl -O https://raw.githubusercontent.com/trsdn/mcp-server-ppt/main/.github/instructions/architecture-patterns.instructions.mdgit clone --depth 1 https://github.com/trsdn/mcp-server-pptWrote 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/trsdn/mcp-server-ppt/architecture-patterns)<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/architecture-patterns"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/architecture-patterns/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/trsdn/mcp-server-ppt/architecture-patterns"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/architecture-patterns.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.01687 | $0.01687 |
| Opus 5.5 | $0.00675 | $0.00675 |
| Sonnet 5.5 | $0.00337 | $0.00337 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
mcp-server-ppt architecture-patterns.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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Patterns
Core patterns for PptMcp development
.NET Class Design (MANDATORY)
Official Docs: Framework Design Guidelines, Partial Classes
Key Rules
- One Public Class Per File - Standard .NET practice (System.Text.Json, ASP.NET Core, EF Core)
- File Name = Class Name -
RangeCommands.cscontainsRangeCommands - Partial Classes for Large Implementations - Split 15+ method classes by feature domain
- Descriptive Names - No over-optimization (
RangeCommands✅,Commands❌) - Folder = Organization, Not Identity -
Commands/Range/RangeCommands.cs
Partial Class Pattern
When: Class has 15+ methods, multiple feature domains, team collaboration
Structure:
Commands/Range/
IRangeCommands.cs # Interface
RangeCommands.cs # Partial (constructor, DI)
RangeCommands.Values.cs # Partial (Get/Set values)
RangeCommands.Formulas.cs # Partial (formulas)
RangeHelpers.cs # Separate helper class
Benefits: Git-friendly, team-friendly, ~100-200 lines per file, mirrors .NET Framework patterns
TWO EQUAL ENTRY POINTS (CRITICAL)
PptMcp has TWO first-class entry points: MCP Server AND CLI. Both must have:
- Feature parity: Every action in MCP must exist in CLI and vice versa
- Parameter parity: Same parameters, same defaults, same validation
- Behavior parity: Same Core command, same result format
When adding or changing ANY feature, ALWAYS update BOTH entry points. See Rule 24 (Post-Change Sync).
MCP Server (MCP tools, JSON-RPC) ──► In-process PptMcpService ──► Core Commands ──► PowerPoint COM
CLI (command-line args, console) ──► CLI Daemon (named pipe) ─────► Core Commands ──► PowerPoint COM
Command Pattern
Structure
Commands/
├── ISlideCommands.cs # Interface
├── SlideCommands.cs # Implementation
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.
- 1mo ago First seen · 231 lines · 1,687 tokens per session scan A 9e7fa635deaa
mcp-server-ppt architecture-patterns.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,687 tokens to every session, about $0.0067 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.