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 skills/zhpeng24/devkit/pptxnpx skills add zhpeng24/devkit --skill pptxgit clone --depth 1 https://github.com/zhpeng24/devkitWhat 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.00047 | $0.01056 |
| Opus 5 | $0.00023 | $0.00528 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
pptx 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerPoint Artifacts
Work on the PowerPoint file itself. Preserve source artifacts, choose tools from the actual environment, and verify structure, content, and rendered slides before claiming completion.
Route the task
| Mode | Goal |
|---|---|
| Inspect/read | Extract slide order, text, notes, media, layouts, and document properties without changing the file. |
| Create | Build a new deck from supplied content, brand rules, and an explicit slide outline. |
| Edit/template | Use the supplied deck or template, preserve its masters and layout language, and write a new output file. |
| Repository report | Build a weekly, monthly, project-status, architecture, MVP, or release deck from traceable repository evidence. |
Generic presentation advice without a .pptx or .potx deliverable is outside this skill.
Preflight
- Resolve the input and explicit output paths. Never overwrite the input unless the user clearly authorizes it.
- Inspect the project for an existing PowerPoint library and lockfile.
- Use a compatible installed option—such as PptxGenJS, python-pptx, or Open XML tooling—rather than assuming a package is present. Add and pin a dependency only when normal project work authorizes it.
- Detect renderers independently. LibreOffice, PowerPoint, or another renderer may be absent; record that limitation instead of claiming visual verification.
- Use a task-scoped temporary directory for extracted or rendered files. Reject archive entries that escape it.
- For repository reports, read
.devkit/project.jsonandreferences/repository-reporting.mdbefore collecting data or choosing cadence.
Inspect or edit
Treat .pptx as an Open Packaging Convention ZIP package. Before editing, inventory slide order, size, masters, layouts, theme, relationships, notes, comments, charts, media, and embedded objects.
Prefer library-level operations. Preserve unfamiliar or unsupported parts and their relationships rather than rebuilding the package from a lossy subset. When a requested edit risks dropping animation, charts, embedded media, macros, or template behavior, state the risk before changing it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 81 lines · 47 tokens per session scan A ce42fbd77249
pptx is a skill published in the GitHub repository zhpeng24/devkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,056 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…