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/critical-rules.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/critical-rules)<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/critical-rules"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/critical-rules/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/critical-rules"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/critical-rules.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.12739 | $0.12739 |
| Opus 5.5 | $0.05096 | $0.05096 |
| Sonnet 5.5 | $0.02548 | $0.02548 |
| Haiku 4.5 | $0.01274 | $0.01274 |
Grade A, and why
mcp-server-ppt critical-rules.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 — 1,279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL RULES - MUST FOLLOW
⚠️ NON-NEGOTIABLE rules for all PptMcp development
Rule 0: NEVER Commit Without Running Tests (CRITICAL)
NEVER commit, push, or create PRs without first running tests for the code you changed.
Why Critical: Prevents breaking changes from reaching main, wastes team time debugging failures, violates CI/CD principles.
Enforcement:
- ALWAYS run relevant tests BEFORE committing
- Use
--filter "Feature=<feature-name>&RunType!=OnDemand"for feature-specific tests - Build must pass (0 warnings, 0 errors)
- Pre-commit hooks must pass (COM leaks, success flag, coverage)
- Document test results in commit message
Process:
- Make code changes
- Build:
dotnet build(must succeed with 0 warnings) - Run tests:
dotnet test --filter "Feature=<feature>&RunType!=OnDemand" - Verify all tests pass
- Run pre-commit checks
- THEN commit
Rule 26: No Confidential Information in Commits/PRs (CRITICAL)
NEVER include confidential project names, file names, customer names, or internal references in commit messages, PR descriptions, or issue descriptions.
Why Critical: Git history and GitHub issues/PRs are public or semi-public. Confidential information in commits persists forever in git history and is difficult to remove.
Forbidden in commits/PRs/issues:
- Customer project names (e.g., "CP Toolkit", "Contoso Deal")
- Specific file paths from customer projects (e.g., "MSX Plan.pptx", "Milestone_Export")
- Internal tool names that reveal customer context
- Any information that could identify a specific customer engagement
Allowed:
- Generic descriptions ("a slide shape", "a PowerPoint presentation")
- Technical details that don't identify the source ("a column with a hyphen in the name")
- Error messages and stack traces (sanitized of paths/names)
Example:
# ❌ WRONG: Reveals confidential project
Discovered while debugging Milestone_Export query in CP Toolkit's MSX Plan.pptx
# ✅ CORRECT: Generic description
Discovered while debugging a slide shape that referenced an embedded object
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 Changed · +96 lines · +1,471 tokens per session 85de2a3705bf
- 1mo ago First seen · 1,183 lines · 11,268 tokens per session scan A 7b57d4c6f6e7
mcp-server-ppt critical-rules.instructions.md is an instructions file published in the GitHub repository trsdn/mcp-server-ppt (41 stars, last pushed yesterday), licensed MIT. It adds 12,739 tokens to every session, about $0.0510 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 powershell.instructions.md
PowerShell best practices for Azure IaC — Az module, script structure, Pester testing, PSScriptAnalyzer.
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).