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/mpuig/agent-slides/slides-editnpx skills add mpuig/agent-slides --skill slides-editgit clone --depth 1 https://github.com/mpuig/agent-slidesWrote 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/skills/mpuig/agent-slides/slides-edit)<a href="https://agentmods.dev/skills/mpuig/agent-slides/slides-edit"><img src="https://agentmods.dev/badge/skills/mpuig/agent-slides/slides-edit.svg" alt="Measured on agentmods" 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 | $0.00081 | $0.01292 |
| Opus 5 | $0.00041 | $0.00646 |
| Sonnet 5 | $0.00016 | $0.00258 |
| Haiku 4.5 | $0.00008 | $0.00129 |
Grade A, and why
slides-edit 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 4d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slides Edit
You are a slide editor. Your job is to make precise, targeted changes to existing decks without breaking what already works.
Modify an existing deck — text changes, layout transforms, and structural edits.
When to Use
- Fix typos or update text in an existing deck
- Apply archetype transforms to restyle slides
- Add/remove/move slides via ops patches
- Any targeted modification that doesn't require a full rebuild
Prerequisites
- An existing
output.pptxin a project directory - Optionally:
slides.json(for context) anddesign-profile.json(for QA)
Step 0) Find the project directory
Ask the user which project to edit, or discover it:
find . -name "design-profile.json" -maxdepth 3
All subsequent commands run from within the project directory.
Process
Step 1) Locate targets
Inspect the deck to find slide/shape UIDs:
uvx --from agent-slides slides inspect output.pptx \
--fields slides.slide_uid,slides.shapes.shape_uid,slides.title \
--out ids.json --compact
Search for specific text:
uvx --from agent-slides slides find output.pptx --query "<search text>" --limit 10 \
--out find.json --compact
Pagination for large decks:
uvx --from agent-slides slides inspect output.pptx --page-size 5 --page-token 0 --compact
Other inspection:
uvx --from agent-slides slides inspect output.pptx --placeholders 0 --compact # placeholders on slide 0
uvx --from agent-slides slides inspect output.pptx --summary --compact # deck summary
Step 2) Pre-edit assessment
Before making changes, briefly note:
- What works well in the current deck (preserve these strengths)
- Scope of change — which slides are affected and which are untouched
- Risk — could this edit break layout, contrast, or narrative flow?
This prevents over-editing and protects existing quality.
Step 3) Apply changes
Text edits (find-and-replace scoped by UID):
uvx --from agent-slides slides edit output.pptx --query "old text" \
--replacement "new text" --slide-uid "<slide_uid>" \
--shape-uid "<shape_uid>" --output output.pptx --compact
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.
- 4d ago First seen · 154 lines · 81 tokens per session scan A dccece9f8781
slides-edit is a skill published in the GitHub repository mpuig/agent-slides (10 stars, last pushed 5mo ago), licensed MIT. It adds 81 tokens to every session and 1,292 once invoked, about $0.0004 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
doc-review
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.
de-ai-flavor
Remove AI artifacts from documents. Use when: cleaning AI-generated text, removing tool names, fixing boilerplate patterns. Not for: doc review (use doc-review), doc refactoring (use doc-refactor). Output: cleaned document preserving original intent.
recap-ask
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap- .md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
request-tracking
Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking.
tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.