powerpoint-python-pptx-mcp tools.instructions.md

Development instructions for building MCP tools that process PowerPoint files with Python.

In plain words
What is it for?
Use them when adding or maintaining tools for slide and speaker-note operations in the PowerPoint MCP server.
Why use it?
They set rules for validating inputs, handling file paths and errors, avoiding blocked operations, and returning predictable results.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/ytthuan/powerpoint-python-pptx-mcp/tools
Clone the repo
git clone --depth 1 https://github.com/ytthuan/powerpoint-python-pptx-mcp

Made for: GitHub Copilot.

Per session 908 This file is loaded in full into every session.
When invoked 908 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00908 $0.00908
Opus 5 $0.00454 $0.00454
Sonnet 5 $0.00182 $0.00182
Haiku 4.5 $0.00091 $0.00091

Measured yesterday against content hash ebe644d6d81b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

powerpoint-python-pptx-mcp tools.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 yesterday.

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.

.github/instructions/tools.instructions.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Tools Development

These instructions apply to all MCP tool implementations in src/mcp_server/tools/.

Critical requirements

  • All tools must validate inputs using mcp_server.utils.validators
  • All tools must use async/await (never block the event loop)
  • All tools must return structured dictionaries with success key
  • All file paths must be validated (no path traversal)
  • All tools must handle errors gracefully with custom exceptions

Tool structure pattern

from typing import Dict, Any
from mcp_server.utils.validators import validate_file_path, validate_slide_number
from mcp_server.exceptions import ValidationError, FileOperationError

async def handle_tool_name(arguments: Dict[str, Any]) -> Dict[str, Any]:
    """Handle MCP tool request for [specific operation].
    
    Args:
        arguments: Tool arguments from MCP client containing:
            - required_param: Description
            - optional_param: Description (optional)
        
    Returns:
        Dictionary with:
            - success (bool): Operation success status
            - data (Any): Tool result data
            - message (str): Optional status message
        
    Raises:
        ValidationError: If arguments are invalid
        FileOperationError: If file operation fails
    """
    try:
        # 1. Validate inputs
        pptx_path = arguments.get("pptx_path")
        validate_file_path(pptx_path)
        
        # 2. Get service from container
        service = get_service_from_container()
        
        # 3. Perform operation
        result = await service.operation(pptx_path)
        
        # 4. Return structured result
        return {
            "success": True,
            "data": result,
            "message": "Operation completed successfully"
        }
        
    except ValidationError as e:
        return {
            "success": False,
            "error": str(e),
            "error_type": "validation_error"
        }
    except Exception as e:
        # Log full exception details server-side for debugging
        logger.error(f"Unexpected error in tool", exc_info=True)
        return {
            "success": False,
            "error": "An unexpected internal error occurred. Please try again later.",
            "error_type": "internal_error"
        }

Read the full file on GitHub · 149 lines

Changes

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.

  1. yesterday First seen · 149 lines · 908 tokens per session scan A ebe644d6d81b

Subscribe to this mod's changes

powerpoint-python-pptx-mcp tools.instructions.md is an instructions file published in the GitHub repository ytthuan/powerpoint-python-pptx-mcp (0 stars, last pushed 7mo ago), licensed MIT. It adds 908 tokens to every session, about $0.0045 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens