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 agents/kimtth/agent-pptify-kit/pptx-buildergit clone --depth 1 https://github.com/kimtth/agent-pptify-kitWhat 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.00022 | $0.01526 |
| Opus 5 | $0.00011 | $0.00763 |
| Sonnet 5 | $0.00004 | $0.00305 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
pptx-builder 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PPTX Builder
Create editable PowerPoint decks. Use native text, shapes, lines, tables,
connectors, and images. Keep the JSON layout tree as the source of truth and
use a small, task-specific python-pptx builder only when a PPTX file is
required.
Non-Negotiable Output Rules
- Build editable slides. Do not use a full-slide image as the slide's content.
- Use native PowerPoint objects for titles, body text, metrics, tables, diagrams, charts, and other information the user may need to edit.
- Use images only as supporting visuals, such as photographs, logos, textures, or illustrations. An image must not be the only meaningful object on a slide.
- Do not put essential text, data labels, or the only explanation of a diagram inside an image. Recreate that information with native objects.
- Write clear U.S. business English. Use short sentences, common words, direct verbs, and specific claims. Check grammar, spelling, numbers, and titles. Avoid idioms, filler, and placeholder text.
- Keep the implementation small. Do not add a general renderer, a large helper library, or a code-heavy framework.
Related Skills
pptx-deck-context: narrative, source material, and design contextpptx-slide-specification: final coordinates and the spec-to-PPTX contractpptx-visual-assets: permitted asset selection and placementpptx-reference-deck-analysis: read-only reference-deck analysis, safe OOXML inspection, and package validationpptx-quality-gates: build, package, geometry, and accessibility checks
Read the relevant skill before using its rules. If a required reference file is missing, state the path and use only information the user supplied. Do not invent missing brand, source, or accessibility details.
Workflow
Understand the request
- Collect the audience, decision or purpose, slide count, language, source material, brand requirements, and delivery date.
- Ask no more than five focused questions at once. Offer practical defaults for slide count, language, and reference deck when the user has not given them.
- Ask the user to select a narrative framework when one is not supplied. Do not select one without the user's approval.
- If a topic alone cannot support a credible deck, ask one direct question for the missing decision, audience, or source facts. Do not add placeholder text.
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 · 133 lines · 22 tokens per session scan A 7b54a4087cb7
pptx-builder is an agent published in the GitHub repository kimtth/agent-pptify-kit (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,526 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Slides Wizard
Expert presentation strategist and creative advisor for creating impactful Marp presentations with strategic content and visual design.
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
oss-growth-hacker
OSS adoption and growth-hacking specialist for microsoft/apm. Activate for README/docs conversion work, launch tactics, contributor funnel, story angles, and to feed reviewed changes into the maintained growth strategy at WIP/growth-strategy.md.