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/ytthuan/powerpoint-python-pptx-mcp/coregit clone --depth 1 https://github.com/ytthuan/powerpoint-python-pptx-mcpWhat 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.02035 | $0.02035 |
| Opus 5 | $0.01018 | $0.01018 |
| Sonnet 5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
powerpoint-python-pptx-mcp core.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.
How it starts
The opening of the file, as written. The whole thing — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Services Development
These instructions apply to core service implementations in src/mcp_server/core/.
Core services overview
Core services provide the fundamental PPTX manipulation capabilities. They must be:
- Reliable: No data loss, no corruption
- Safe: Validate all inputs, handle all errors
- Efficient: Use caching, lazy loading
- Maintainable: Clear abstractions, well-tested
Critical requirements
- Never modify PPTX structure accidentally - Preserve animations, transitions, layouts
- Always validate file integrity - Check PPTX is valid before and after operations
- Use context managers - Properly close file handles
- Handle encoding carefully - Support Unicode (especially Vietnamese characters)
- Log all operations - Structured logging with context
PPTX Handler pattern
from typing import Optional, List, Dict, Any
from pptx import Presentation
from pathlib import Path
import logging
logger = logging.getLogger(__name__)
class PPTXHandler:
"""Handle PPTX file operations safely and efficiently."""
def __init__(self, cache_size: int = 100):
"""Initialize handler with optional caching.
Args:
cache_size: Maximum number of presentations to cache
"""
self._cache = LRUCache(cache_size)
async def read_presentation(
self,
pptx_path: str,
use_cache: bool = True
) -> Presentation:
"""Read presentation from file with optional caching.
Args:
pptx_path: Path to PPTX file
use_cache: Whether to use cache
Returns:
Presentation object
Raises:
FileOperationError: If file cannot be read
"""
try:
# Check cache first
if use_cache and pptx_path in self._cache:
logger.debug(f"Cache hit for {pptx_path}")
return self._cache[pptx_path]
# Validate file exists and is readable
path = Path(pptx_path)
if not path.exists():
raise FileOperationError(f"File not found: {pptx_path}")
# Load presentation
logger.info(f"Loading presentation: {pptx_path}")
prs = Presentation(pptx_path)
# Cache if requested
if use_cache:
self._cache[pptx_path] = prs
return prs
except Exception as e:
logger.error(f"Failed to read presentation: {e}", exc_info=True)
raise FileOperationError(f"Cannot read PPTX: {e}")
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.
- yesterday First seen · 336 lines · 2,035 tokens per session scan A a60df888e4d1
powerpoint-python-pptx-mcp core.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 2,035 tokens to every session, about $0.0102 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.
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.
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).
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.
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).
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.
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.