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/seifbenayed/cloclo/pptxnpx skills add SeifBenayed/cloclo --skill pptxgit clone --depth 1 https://github.com/SeifBenayed/clocloWhat 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.00152 | $0.03029 |
| Opus 5 | $0.00076 | $0.01515 |
| Sonnet 5 | $0.00030 | $0.00606 |
| Haiku 4.5 | $0.00015 | $0.00303 |
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 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PPTX Skill
Tool-First Workflow
Use the Presentation tool for ALL operations. Do NOT use Python scripts unless you need features the tool doesn't have.
Available Presentation tool actions
| Task | Tool call |
|---|---|
| Inspect metadata | Presentation { action: "inspect", file_path: "deck.pptx" } |
| List all slides | Presentation { action: "list_slides", file_path: "deck.pptx" } |
| Extract text (all or one slide) | Presentation { action: "extract_text", file_path: "deck.pptx" } |
| Read speaker notes | Presentation { action: "read_notes", file_path: "deck.pptx" } |
| Export text outline | Presentation { action: "export_text_outline", file_path: "deck.pptx" } |
| Create new presentation | Presentation { action: "create", output_path: "deck.pptx", content: {slides: [{title, body: [...]}]} } |
| Unpack for XML editing | Presentation { action: "unpack", file_path: "deck.pptx", output_path: "unpacked/" } |
| Repack after editing | Presentation { action: "pack", file_path: "unpacked/", output_path: "output.pptx" } |
Editing an existing presentation
Presentation { action: "unpack", file_path: "template.pptx", output_path: "/tmp/unpacked/" }
# → Edit slide XML files in /tmp/unpacked/ppt/slides/ with the Edit tool
# → Reorder slides by editing /tmp/unpacked/ppt/presentation.xml
Presentation { action: "pack", file_path: "/tmp/unpacked/", output_path: "output.pptx" }
Creating from scratch
Presentation { action: "create", output_path: "deck.pptx", content: {
"layout": "16x9",
"slides": [
{"title": "Welcome", "body": ["Point 1", "Point 2", "Point 3"]},
{"title": "Details", "body": ["Item A", "Item B"], "notes": "Speaker notes here"}
]
}}
For advanced presentations (charts, images, custom layouts), use PptxGenJS via Bash — see pptxgenjs.md.
When to fall back to Python
- Thumbnail grids (requires LibreOffice + PIL)
- Converting PPTX to PDF (requires LibreOffice)
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 · 269 lines · 152 tokens per session scan A 50c64d532001
pptx is a skill published in the GitHub repository SeifBenayed/cloclo (114 stars, last pushed 4mo ago), licensed MIT. It adds 152 tokens to every session and 3,029 once invoked, about $0.0008 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.