Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/trsdn/mcp-server-ppt/readme-managementgit 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.svg" alt="Measured on agentmods" 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 | $0.00770 | $0.00770 |
| Sonnet 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 5d 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.
- 5d 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 (36 stars, last pushed yesterday), licensed MIT. It adds 1,540 tokens to every session, about $0.0077 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
langgraph AGENTS.md
AGENTS.md instructions for langchain-ai/langgraph, covering agents instructions, corridor security analysis, libraries and dependency map.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
AstrBot copilot-instructions.md
Copilot instructions for AstrBotDevs/AstrBot, covering astrbot development instructions, working effectively, bootstrap and install dependencies, running the application and dashboard build (vue.js/node.js).
mcp-dotnet-samples AGENTS.md
AGENTS.md instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.
moorestech AGENTS.md
AGENTS.md instructions for moorestech/moorestech, covering コーディングの指針, qa（必須）, 互換性とパフォーマンス, 既知の制約（設計上の割り切り） and regionの活用.
nina AGENTS.md
AGENTS.md instructions for isbeorn/nina, covering agents.md, scope, documentation boundary, repository knowledge and code style and formatting.