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/readme-management.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/readme-management)<a href="https://agentmods.dev/instructions/trsdn/mcp-server-ppt/readme-management"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/readme-management/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/readme-management"><img src="https://agentmods.dev/badge/instructions/trsdn/mcp-server-ppt/readme-management.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.01540 | $0.01540 |
| Opus 5.5 | $0.00616 | $0.00616 |
| Sonnet 5.5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
mcp-server-ppt readme-management.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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
README Management - Quick Reference
Four READMEs
| File | Lines | Audience | Purpose |
|---|---|---|---|
/README.md |
250-300 | All users | Comprehensive reference |
/src/PptMcp.McpServer/README.md |
80-100 | .NET devs | Concise NuGet gateway |
/vscode-extension/README.md |
100-120 | VS Code users | User benefits focus |
/gh-pages/index.md |
450-5000 | All users | Comprehensive reference |
Features.md
You need to make sure that the Features.md file is up-to-date with the latest features of the project. This file should be updated whenever a new feature is added or an existing feature is modified.
Critical Rules
Tool & Action Counts Must Match
⚠️ IMPORTANT: CLI has FEWER tools/operations than MCP Server!
ALWAYS count tools/operations BEFORE updating any README. Never use hardcoded numbers from memory.
Before updating counts, verify by counting:
- MCP Server: Count tool files (ppt_batch handled via PptTools.cs, not separate tool file)
- CLI: Count command group folders (includes Session commands)
- Operations: Count separately for each - they differ!
Sync counts across:
- GitHub Project About: https://github.com/trsdn/mcp-server-ppt (use the GitHub CLI to update)
/README.md/src/PptMcp.McpServer/README.md/src/PptMcp.CLI/README.md/vscode-extension/README.md/gh-pages/index.md/FEATURES.md
Operation Lists Must Be Complete
⚠️ IMPORTANT: Where operation lists are documented, they MUST match the actual code!
The gh-pages/index.md file contains detailed tables of all operations for each tool. When adding/removing operations:
- Verify section header count matches actual operation count in code
- Verify each operation is listed in the table - no missing or extra entries
- Verify operation names match the code (kebab-case in docs, PascalCase in code)
Common discrepancies found:
- Section header says "25 actions" but code has 30
- Table lists operations that don't exist (stale documentation)
- Table is missing newly added operations
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 · 161 lines · 1,540 tokens per session scan A aae057890813
mcp-server-ppt readme-management.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,540 tokens to every session, about $0.0062 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.