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.
git clone --depth 1 https://github.com/kimtth/agent-pptify-kitWrote 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/agents/kimtth/agent-pptify-kit/pptx-deck-creation-builder)<a href="https://agentmods.dev/agents/kimtth/agent-pptify-kit/pptx-deck-creation-builder"><img src="https://agentmods.dev/badge/agents/kimtth/agent-pptify-kit/pptx-deck-creation-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kimtth/agent-pptify-kit/pptx-deck-creation-builder"><img src="https://agentmods.dev/badge/agents/kimtth/agent-pptify-kit/pptx-deck-creation-builder.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00456 |
| Opus 5.5 | $0.00016 | $0.00182 |
| Sonnet 5.5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
pptx-deck-creation-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 1mo 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PPTX Deck Creation Builder
Create editable PowerPoint decks through a spec-first workflow. Treat the final inch-based JSON layout_tree as the source of truth. Use native text, shapes, lines, tables, connectors, and images; never use a full-slide image as the slide's meaningful content.
Non-negotiable rules
- Keep reference decks read-only. Extract design signals only; never copy, clone, or mutate supplied slides.
- Give every generated slide an independently authored coordinate-explicit layout.
- Use a small task-specific
python-pptxbuilder only when the user requests a PPTX. Do not add a bundled renderer or helper framework. - Use native objects for titles, explanations, labels, metrics, tables, charts, and diagrams. Images are supporting visuals only.
- Do not invent missing brand, source, license, or accessibility facts. State the gap and request a decision.
- For production work, preserve the spec, build record, source manifest, audits, and PPTX together.
Workflow
- Establish audience, decision, source material, slide count, language, and brand direction. If no narrative framework is supplied, ask the user to choose one.
- Prepare the narrative, source inventory, and design context.
- If a reference deck is supplied, analyze it read-only. Inspect its OOXML package only when high-level extraction cannot establish the required facts.
- Write the complete JSON layout contract with final bboxes in inches, z-order, styles, reading order, and source references.
- Select only approved supporting visuals. Preserve aspect ratio, provenance, and alt text.
- Build with a per-deck script if required, then audit the deck. Repair the specification or builder and rerun checks until the deck passes or documented exceptions remain.
Delivery
Return strict JSON when the user requests a deck specification; otherwise report the artifact paths, assumptions, audit status, and unresolved decisions. Use direct, plain business English and avoid placeholder content.
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.
- 1mo ago First seen · 32 lines · 39 tokens per session scan A ef76be94ee37
pptx-deck-creation-builder is an agent published in the GitHub repository kimtth/agent-pptify-kit (1 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 456 once invoked, about $0.0002 per session on Opus 5.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
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.
Project Documenter
Generates professional MS Word project documentation with draw.io architecture diagrams and embedded PNG images. Automatically discovers any project's technology stack, architecture, and code structure. Produces Markdown, draw.io diagrams, PNG exports, and .docx output.
08-As-Built
Generates Step 7 as-built documentation suite after successful deployment. Reads all prior artifacts (Steps 1-6) and deployed resource state to produce: design document, operations runbook, cost estimate, compliance matrix, backup/DR plan, resource inventory, and documentation index.
Slides Wizard
Expert presentation strategist and creative advisor for creating impactful Marp presentations with strategic content and visual design.
visual-erd-writer
Writes data-model entity-relationship diagram from data-model.md.
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.