Borrowing it
Nothing to install: this file belongs to dnvriend/pdf-to-pptx-tool. 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/dnvriend/pdf-to-pptx-tool/main/CLAUDE.mdgit clone --depth 1 https://github.com/dnvriend/pdf-to-pptx-toolWrote 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/dnvriend/pdf-to-pptx-tool/claude-md)<a href="https://agentmods.dev/instructions/dnvriend/pdf-to-pptx-tool/claude-md"><img src="https://agentmods.dev/badge/instructions/dnvriend/pdf-to-pptx-tool/claude-md.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.02302 | $0.02302 |
| Opus 5 | $0.01151 | $0.01151 |
| Sonnet 5 | $0.00460 | $0.00460 |
| Haiku 4.5 | $0.00230 | $0.00230 |
Grade A, and why
pdf-to-pptx-tool CLAUDE.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 8d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pdf-to-pptx-tool - Project Specification
Goal
Convert PDF documents into PowerPoint presentations with customizable quality settings, professional output format, and comprehensive debugging capabilities.
What is pdf-to-pptx-tool?
pdf-to-pptx-tool is a professional command-line utility that converts PDF files to PowerPoint (PPTX) format. Each PDF page becomes a full-slide image in a 16:9 widescreen presentation. Built with modern Python tooling and best practices, it features multi-level verbosity logging, shell completion, and type-safe code.
Technical Requirements
Runtime
- Python 3.14+
- Installable globally with mise
- Cross-platform (macOS, Linux, Windows)
Dependencies
click- CLI frameworkpdf2image- PDF to image conversionpython-pptx- PowerPoint file creationPillow- Image processingpoppler- System library for PDF rendering (external dependency)
Development Dependencies
ruff- Linting and formattingmypy- Type checkingpytest- Testing frameworkbandit- Security lintingpip-audit- Dependency vulnerability scanninggitleaks- Secret detection (requires separate installation)
CLI Commands
Main Command
pdf-to-pptx-tool [OPTIONS] COMMAND [ARGS]
Global Options:
-v, --verbose- Enable verbose output (count flag: -v, -vv, -vvv)-v(count=1): INFO level logging-vv(count=2): DEBUG level logging-vvv(count=3+): TRACE level (includes library internals for pdf2image, PIL, pptx)
--version- Show version--help- Show help message
convert - Convert PDF to PowerPoint
pdf-to-pptx-tool convert INPUT_PDF OUTPUT_PPTX [OPTIONS]
Arguments:
INPUT_PDF- Path to input PDF file (required)OUTPUT_PPTX- Path to output PPTX file (required)
Options:
--dpi INTEGER- Resolution for PDF page conversion (default: 200)- Range: 72-600 DPI
- Higher DPI = better quality but larger files
- Recommended: 200-300 for presentations
- Examples: 72 (draft), 150 (web), 200 (default), 300 (print), 600 (high-res)
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.
- 8d ago First seen · 322 lines · 2,302 tokens per session scan A 1b245acc7ccd
pdf-to-pptx-tool CLAUDE.md is an instructions file published in the GitHub repository dnvriend/pdf-to-pptx-tool (2 stars, last pushed 9mo ago), licensed MIT. It adds 2,302 tokens to every session, about $0.0115 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
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.
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.
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).
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).
langchain AGENTS.md
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.
spec-kit AGENTS.md
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.