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/development-workflowgit clone --depth 1 https://github.com/trsdn/mcp-server-pptWhat 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 | $0.01082 | $0.01082 |
| Opus 5 | $0.00541 | $0.00541 |
| Sonnet 5 | $0.00216 | $0.00216 |
| Haiku 4.5 | $0.00108 | $0.00108 |
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 2d 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 — 114 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
- Create feature branch:
git checkout -b feature/name - Standards: Zero warnings, tests pass, docs updated, security rules followed
- PR Checklist: Build passes, tests pass, docs updated, patterns followed
- Check PR review comments: After creating PR, retrieve automated review feedback and fix all issues
- 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.
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.
- 2d ago First seen · 114 lines · 1,082 tokens per session scan A 6b055e013130
mcp-server-ppt development-workflow.instructions.md is an instructions file published in the GitHub repository trsdn/mcp-server-ppt (36 stars, last pushed 7d ago), licensed MIT. It adds 1,082 tokens to every session, about $0.0054 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.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
gptme AGENTS.md
AGENTS.md instructions for gptme/gptme, covering agent instructions for gptme, git workflow, code style, testing and project structure.
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
Instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.
chatgpt-cli CLAUDE.md
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.