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 current-slidegit 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/current-slide)<a href="https://agentmods.dev/skills/shennawardana23/skillme/current-slide"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/current-slide/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/current-slide"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/current-slide.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.00110 | $0.01614 |
| Opus 5.5 | $0.00044 | $0.00646 |
| Sonnet 5.5 | $0.00022 | $0.00323 |
| Haiku 4.5 | $0.00011 | $0.00161 |
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 9d 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
100% identical to current-slide — 0 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 — 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 underslides/. Use as-is for any/__slides/<id>/...API or as the URL segment.pageIndex— 0-based, for use with the page array inindex.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 toRead/Edit.view—"slides"(canvas view) or"assets"(asset manager). If"assets", the user is browsing files for that slide rather than viewing a page.selection—nullif nothing is selected. Otherwise, the JSX element the user picked in the inspector overlay:line(1-indexed) andcolumn(0-indexed) point to the JSX opening tag insidepagePath. This is the canonical handle — match against the source line, not the rendered DOM.tagNameis the rendered DOM tag, lowercased ("h1","div","img").textis a trimmed text snippet (≤120 chars) from the element'stextContent, 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.
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.
- 9d ago First seen · 111 lines · 110 tokens per session scan A c58ccbd0177c
current-slide is a skill published in the GitHub repository shennawardana23/skillme (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 110 tokens to every session and 1,614 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to current-slide, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
handoff
Distills the current session's goal, state, remaining plan, key files, and gotchas into a copy-pasteable markdown handoff for a fresh agent or teammate, written to .agent/{branch}/handoff.md and the clipboard. Invoke with /handoff [focus phrase] [--brief].
life-design
Walk you through the Stanford Designing Your Life method and write your Personal Life Design Blueprint — three Odyssey plans and the prototypes to test them.
disk-cleaner
A Mac disk-cleaning assistant built around the Mole cleanup tool. It checks the environment, previews removable files, and can run cleanup using different safety levels with reports and protected paths.
timeboxed-work
Work under an explicit time budget with deterministic deadline tracking, useful stretch work, scope control, isolated timers for parallel sessions/agents/apps, and handoff. Use when the user asks for a timebox, fixed duration, deadline, work for N minutes/hours, use the full time, keep improving until the deadline…
lockin
Lock in on a goal that can be checked and work autonomously until it's provably met or a cap is hit, looping act → prove → judge. Use when the user runs /lockin, says "lock in", "keep going until…", "don't stop until…", or hands over a task with a clear finish line (tests pass, build green, queue empty).
lark-meeting
A tool for finding and working with online meeting records and related documents in Lark, a workplace collaboration platform. It handles summaries, transcripts, recordings, searchable meeting notes, and live meeting interaction.