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/xyruscode/ai-sync/kimi-slidesnpx skills add XyrusCode/ai-sync --skill kimi-slidesgit clone --depth 1 https://github.com/XyrusCode/ai-syncWhat 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.00099 | $0.01724 |
| Opus 5 | $0.00049 | $0.00862 |
| Sonnet 5 | $0.00020 | $0.00345 |
| Haiku 4.5 | $0.00010 | $0.00172 |
Grade A, and why
kimi-slides 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Definition
kimi-slides is a ppt-generation skill built by Moonshot AI as a first-party skill. It defines a YAML-format intermediate DSL (.pptd) that further abstracts OOXML, making presentation generation effortless. The DSL can be used to generate and render PPTs, and existing pptx files can also be converted into this DSL for editing.
The pptd format
The .pptd format is a simplified abstraction layer over OOXML that follows basic YAML syntax. This abstraction preserves the core content of OOXML (theme, page layout, element positions and definitions, etc.) while removing complex nesting logic such as Masters; every page is self-contained — what you see is what you get. Read reference/pptd.md for the complete definition of this DSL.
Companion CLI
The skill also ships with a companion CLI tool (pre-installed in the environment) for two-way conversion between pptd and pptx, pptd validation, pptd/pptx screenshot rendering, and more. Read reference/cli.md for the complete CLI usage instructions.
PPT production workflow
step1. Read the context thoroughly
Read all files uploaded by the user, the provided URLs, and the pptd format guide reference/pptd.md to fully understand the user's requirements.
step2. Understand the user's requirements
Understand the user's requirements based on the context:
- First determine the purpose of the request
- Create a PPT: create a new presentation (from scratch, or from an existing pptx template)
- Edit a PPT: edit the user's uploaded PPT (local modifications, single-page beautification, etc.)
- Replicate a PPT: replicate a presentation from a non-pptx format (images, PDF, etc.) into pptx format
- Then determine the design direction
- Self-directed design: no preference, or only simple style constraints given; you need to fill in or create the design
- Design system: the user provides a complete and detailed design scheme covering all color, font, layout, and component specifications
- Use a template: a template is provided and must be used
- Style transfer: a style reference source is provided (images, web pages, etc.)
What ships with it
13 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.
- reference/cli.md 5.4 KB
- reference/fonts.md 4.8 KB
- reference/general-poster.md 27 KB
- reference/pptd.md 79 KB
- reference/shapes.md 15 KB
- reference/slides_categories.md 4.7 KB
- reference/slides_categories/academic-research.md 15 KB
- reference/slides_categories/analysis-decision.md 5.8 KB
- reference/slides_categories/brand-creative.md 14 KB
- reference/slides_categories/business-plan.md 6.2 KB
- reference/slides_categories/education-training.md 24 KB
- reference/slides_categories/management-report.md 5.4 KB
- reference/slides_categories/tech-engineering.md 18 KB
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 · 97 lines · 99 tokens per session scan A b69906558f14
kimi-slides is a skill published in the GitHub repository XyrusCode/ai-sync (2 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 1,724 once invoked, about $0.0005 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…