current-slide

current-slide is a skill for Claude Code, Codex from 1weiho/open-slide. It costs 110 tokens per session (1,614 once invoked), scanned A, original, MIT.

A tool for finding the exact slide, page, or selected object that a user is currently viewing in an open-slide development server.

In plain words
What is it for?
Use it before responding to requests about the current slide, page, heading, or selected element.
Why use it?
It prevents an edit from being applied to the wrong slide when the user refers to “this page” or “the element I’m looking at.”

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

About the project

open-slide is a React-based slide framework that lets coding agents create presentations from natural-language descriptions. It provides the canvas, scaling, navigation, hot reload, and presentation mode while agents write the slide components. The catalogue skills and instructions support agent-based slide authoring and revision.

1weiho/open-slide · 7,393 stars · on GitHub · open-slide.dev

Install

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.

agentmods
npx agentmods add skills/1weiho/open-slide/current-slide
Any agent
npx skills add 1weiho/open-slide --skill current-slide
Clone the repo
git clone --depth 1 https://github.com/1weiho/open-slide

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for current-slide

README.md
[![agentmods](https://agentmods.dev/badge/skills/1weiho/open-slide/current-slide.svg)](https://agentmods.dev/skills/1weiho/open-slide/current-slide)
Your own site
<a href="https://agentmods.dev/skills/1weiho/open-slide/current-slide"><img src="https://agentmods.dev/badge/skills/1weiho/open-slide/current-slide.svg" alt="Measured on agentmods" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,614 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00110 $0.01614
Opus 5 $0.00055 $0.00807
Sonnet 5 $0.00022 $0.00323
Haiku 4.5 $0.00011 $0.00161

Measured 7d ago against content hash c58ccbd0177c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

current-slide 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 7d 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.

packages/core/skills/current-slide/SKILL.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Where is the user right now?

When the user says "fix this page", "tweak this heading", or "the slide I'm looking at", they almost never name the slide id, page number, or element — they mean wherever they are in the dev viewer. Before asking "which slide?" or "which element?", check the file the dev server writes on every navigation and inspector pick.

Re-read on every deictic turn — never reuse a prior read

current.json is a live cursor, not a fact about the conversation. The user moves between slides, pages, and elements freely between your turns — including while you were doing other work. Read the file fresh at the start of every new turn that uses a deictic reference, even if:

  • you already read it earlier in this same conversation,
  • you just finished editing the slide it pointed to,
  • the user's new message sounds like a continuation ("now make it bigger", "also fix this one", "keep going").

A "continue editing" follow-up is exactly the case where the user has likely just navigated to a different slide or picked a different element. Trusting your last read here will silently edit the wrong file. Re-read, compare slideId / pageIndex / selection against what you used last time, and act on the new values.

How to read it

node_modules/.open-slide/current.json

Path is relative to the project root (the user's cwd, the directory that contains slides/ and package.json). Use the Read tool. The file is JSON.

What you get

{
  "slideId": "q2-roadmap",
  "pageIndex": 2,
  "pageNumber": 3,
  "totalPages": 8,
  "slideTitle": "Q2 Roadmap",
  "view": "slides",
  "pagePath": "slides/q2-roadmap/index.tsx",
  "selection": {
    "line": 42,
    "column": 6,
    "tagName": "h1",
    "text": "Q2 Roadmap"
  },
  "updatedAt": "2026-05-09T14:32:11.123Z"
}
  • slideId — folder name under slides/. Use as-is for any /__slides/<id>/... API or as the URL segment.
  • pageIndex — 0-based, for use with the page array in index.tsx (export default [Cover, Body, ...]).
  • pageNumber — 1-based, for use in messages to the user ("page 3 of 8") and for the URL ?p=N.
  • pagePath — relative path to the slide source. Hand straight to Read / Edit.
  • view"slides" (canvas view) or "assets" (asset manager). If "assets", the user is browsing files for that slide rather than viewing a page.
  • selectionnull if nothing is selected. Otherwise, the JSX element the user picked in the inspector overlay:
    • line (1-indexed) and column (0-indexed) point to the JSX opening tag inside pagePath. This is the canonical handle — match against the source line, not the rendered DOM.
    • tagName is the rendered DOM tag, lowercased ("h1", "div", "img").
    • text is a trimmed text snippet (≤120 chars) from the element's textContent, useful as a sanity check that you're looking at the right node.
    • Selection auto-clears whenever the user navigates to a different slide or page.
  • updatedAt — ISO timestamp of the last navigation or selection change. Use it to detect staleness.

Read the full file on GitHub · 111 lines

Changes

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.

  1. 7d ago First seen · 111 lines · 110 tokens per session scan A c58ccbd0177c

Subscribe to this mod's changes

current-slide is a skill published in the GitHub repository 1weiho/open-slide (7,393 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 1,614 once invoked, about $0.0006 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.