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/vrsen/openswarm/pptxnpx skills add VRSEN/OpenSwarm --skill pptxgit clone --depth 1 https://github.com/VRSEN/OpenSwarmWhat 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.00062 | $0.06230 |
| Opus 5 | $0.00031 | $0.03115 |
| Sonnet 5 | $0.00012 | $0.01246 |
| Haiku 4.5 | $0.00006 | $0.00623 |
Grade B, and why
pptx scanned grade B with 1 finding 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **LibreOffice**: `sudo apt-get install libreoffice` (for PDF conversion) This is a copy
95% identical to pptx — 206 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PPTX creation, editing, and analysis
Overview
A user may ask you to create, edit, or analyze the contents of a .pptx file. A .pptx file is essentially a ZIP archive containing XML files and other resources that you can read or edit. You have different tools and workflows available for different tasks.
Reading and analyzing content
Text extraction
If you just need to read the text contents of a presentation, you should convert the document to markdown:
# Convert document to markdown
python -m markitdown path-to-file.pptx
Raw XML access
You need raw XML access for: comments, speaker notes, slide layouts, animations, design elements, and complex formatting. For any of these features, you'll need to unpack a presentation and read its raw XML contents.
Unpacking a file
python ooxml/scripts/unpack.py <office_file> <output_dir>
Note: The unpack.py script is located at skills/pptx/ooxml/scripts/unpack.py relative to the project root. If the script doesn't exist at this path, use find . -name "unpack.py" to locate it.
Key file structures
ppt/presentation.xml- Main presentation metadata and slide referencesppt/slides/slide{N}.xml- Individual slide contents (slide1.xml, slide2.xml, etc.)ppt/notesSlides/notesSlide{N}.xml- Speaker notes for each slideppt/comments/modernComment_*.xml- Comments for specific slidesppt/slideLayouts/- Layout templates for slidesppt/slideMasters/- Master slide templatesppt/theme/- Theme and styling informationppt/media/- Images and other media files
Typography and color extraction
When given an example design to emulate: Always analyze the presentation's typography and colors first using the methods below:
- Read theme file: Check
ppt/theme/theme1.xmlfor colors (<a:clrScheme>) and fonts (<a:fontScheme>) - Sample slide content: Examine
ppt/slides/slide1.xmlfor actual font usage (<a:rPr>) and colors - Search for patterns: Use grep to find color (
<a:solidFill>,<a:srgbClr>) and font references across all XML files
What ships with it
54 files 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.
- html2pptx.md 19 KB
- ooxml.md 10 KB
- ooxml/schemas/ecma/fouth-edition/opc-contentTypes.xsd 1.9 KB
- ooxml/schemas/ecma/fouth-edition/opc-coreProperties.xsd 2.5 KB
- ooxml/schemas/ecma/fouth-edition/opc-digSig.xsd 2.8 KB
- ooxml/schemas/ecma/fouth-edition/opc-relationships.xsd 1.3 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-chart.xsd 73 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-chartDrawing.xsd 6.8 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-diagram.xsd 50 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-lockedCanvas.xsd 624 B
- ooxml/schemas/ISO-IEC29500-4_2016/dml-main.xsd 148 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-picture.xsd 1.2 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-spreadsheetDrawing.xsd 8.7 KB
- ooxml/schemas/ISO-IEC29500-4_2016/dml-wordprocessingDrawing.xsd 14 KB
- ooxml/schemas/ISO-IEC29500-4_2016/pml.xsd 82 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-additionalCharacteristics.xsd 1.2 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-bibliography.xsd 7.2 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-commonSimpleTypes.xsd 6.2 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-customXmlDataProperties.xsd 1.2 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-customXmlSchemaProperties.xsd 880 B
- ooxml/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesCustom.xsd 2.5 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesExtended.xsd 3.4 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-documentPropertiesVariantTypes.xsd 7.3 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-math.xsd 23 KB
- ooxml/schemas/ISO-IEC29500-4_2016/shared-relationshipReference.xsd 1.3 KB
- ooxml/schemas/ISO-IEC29500-4_2016/sml.xsd 237 KB
- ooxml/schemas/ISO-IEC29500-4_2016/vml-main.xsd 26 KB
- ooxml/schemas/ISO-IEC29500-4_2016/vml-officeDrawing.xsd 25 KB
- ooxml/schemas/ISO-IEC29500-4_2016/vml-presentationDrawing.xsd 535 B
- ooxml/schemas/ISO-IEC29500-4_2016/vml-spreadsheetDrawing.xsd 5.6 KB
- ooxml/schemas/ISO-IEC29500-4_2016/vml-wordprocessingDrawing.xsd 3.9 KB
- ooxml/schemas/ISO-IEC29500-4_2016/wml.xsd 167 KB
- ooxml/schemas/ISO-IEC29500-4_2016/xml.xsd 4.5 KB
- ooxml/schemas/mce/mc.xsd 3.1 KB
- ooxml/schemas/microsoft/wml-2010.xsd 26 KB
- ooxml/schemas/microsoft/wml-2012.xsd 3.7 KB
- ooxml/schemas/microsoft/wml-2018.xsd 901 B
- ooxml/schemas/microsoft/wml-cex-2018.xsd 1.7 KB
- ooxml/schemas/microsoft/wml-cid-2016.xsd 1002 B
- ooxml/schemas/microsoft/wml-sdtdatahash-2020.xsd 600 B
- ooxml/schemas/microsoft/wml-symex-2015.xsd 745 B
- ooxml/scripts/pack.py 5.8 KB runs code
- ooxml/scripts/unpack.py 1.0 KB runs code
- ooxml/scripts/validate.py 1.9 KB runs code
- ooxml/scripts/validation/__init__.py 336 B runs code
- ooxml/scripts/validation/base.py 39 KB runs code
- ooxml/scripts/validation/docx.py 9.8 KB runs code
- ooxml/scripts/validation/pptx.py 12 KB runs code
- ooxml/scripts/validation/redlining.py 11 KB runs code
- scripts/html2pptx.js 49 KB runs code
- scripts/inventory.py 37 KB runs code
- scripts/rearrange.py 8.3 KB runs code
- scripts/replace.py 13 KB runs code
- scripts/thumbnail.py 15 KB runs code
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.
- 3d ago First seen · 529 lines · 62 tokens per session scan B fb1a51f08123
pptx is a skill published in the GitHub repository VRSEN/OpenSwarm (2,855 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 6,230 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 95% identical to pptx, differing in 206 lines, and is treated as a copy.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…