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 skills add shennawardana23/skillme --skill slide-authoringgit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/slide-authoring)<a href="https://agentmods.dev/skills/shennawardana23/skillme/slide-authoring"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/slide-authoring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/shennawardana23/skillme/slide-authoring"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/slide-authoring.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00146 | $0.05634 |
| Opus 5.5 | $0.00058 | $0.02254 |
| Sonnet 5.5 | $0.00029 | $0.01127 |
| Haiku 4.5 | $0.00015 | $0.00563 |
Grade A, and why
slide-authoring 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 8d 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.
This is a copy
92% identical to slide-authoring — 33 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring open-slide pages
This skill is the technical reference for everything that happens inside slides/<id>/index.tsx. It does not own a workflow:
create-slideowns "draft a new deck" — it asks the user scoping questions, then delegates the how to this skill.apply-commentsowns "process inspector markers" — it finds markers and applies edits, but the edits themselves follow the rules here.current-slideresolves deictic references ("this page", "the slide I'm on") to a concreteslideId+pageIndex. Consult it first when the user references the current slide without naming it, then come back here for how to edit it.- Any ad-hoc slide edit (manual tweak, one-off fix) should also consult this skill before touching the file.
When any of those paths reach the point of writing React code for a page, this is the source of truth. Do not duplicate the knowledge below into other skills — link here instead.
Primitive references
Each framework primitive has a full reference file under references/ in this skill — contract, worked examples, and its own anti-patterns. This file keeps only the always-on rules and a short summary per primitive. Read the relevant reference file before using a primitive on a page:
| Primitive | Read before | File |
|---|---|---|
design const + var(--osd-X) tokens |
writing any new slide (default baseline) | references/design-system.md |
Assets + <ImagePlaceholder> |
importing images/videos or leaving a placeholder | references/assets.md |
| Webfonts | loading any non-system font | references/webfonts.md |
useSlidePageNumber() |
rendering a page-number footer | references/page-numbers.md |
<Steps> / <Step> |
staging a page's reveal | references/steps.md |
SlideTransition |
declaring any enter/exit animation | references/transitions.md |
MorphElement + morph |
morphing a shared element across pages | references/morph.md |
Hard rules
- Put the slide under
slides/<kebab-case-id>/. - Entry is
slides/<id>/index.tsx. Images/videos/fonts go underslides/<id>/assets/. - Do not touch
package.json,open-slide.config.ts, or other slides. - Do not add dependencies. Only
react,@open-slide/core, and standard web APIs are available. - A slide is one
index.tsxplusassets/— nothing else. Do not create sibling.tsx/.tsfiles (Card.tsx,components/,helpers.ts, etc.); helper components and constants go insideindex.tsx. Do not createREADME.mdor other prose files either.
What ships with it
7 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.
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.
- 8d ago First seen · 351 lines · 146 tokens per session scan A 81e1550cdb61
slide-authoring is a skill published in the GitHub repository shennawardana23/skillme (3 stars, last pushed 9d ago), licensed Apache-2.0. It adds 146 tokens to every session and 5,634 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to slide-authoring, differing in 33 lines, and is treated as a copy.
Other skills, from other repositories
effect-best-practices
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
react-bits
Use when adding an animated UI component, text effect, cursor/hover effect, or WebGL/canvas background to a React project via React Bits (reactbits.dev) — or when asked to recall/write a React Bits component's code, props, or install steps from memory instead of fetching it.
clerk-nextjs-patterns
A collection of implementation patterns for adding Clerk authentication to Next.js applications. Clerk is a service that manages user accounts and login sessions.
nextjs-app-router-patterns
A guide to Next.js 14 and later's App Router, a file-based way to organise pages, layouts, loading states, and API endpoints.
remotion-best-practices
Router for all Remotion skills.
nextjs-code-review
A code-review assistant for Next.js applications. Next.js is a framework for building React websites and web applications, including pages that run on the server.