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.
Borrowing it
Nothing to install: this file belongs to 1weiho/open-slide. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/1weiho/open-slide/main/AGENTS.mdgit clone --depth 1 https://github.com/1weiho/open-slideWrote 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/instructions/1weiho/open-slide/agents-md)<a href="https://agentmods.dev/instructions/1weiho/open-slide/agents-md"><img src="https://agentmods.dev/badge/instructions/1weiho/open-slide/agents-md/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/instructions/1weiho/open-slide/agents-md"><img src="https://agentmods.dev/badge/instructions/1weiho/open-slide/agents-md.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.00789 | $0.00789 |
| Opus 5.5 | $0.00316 | $0.00316 |
| Sonnet 5.5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
open-slide AGENTS.md 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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
open-slide — Framework Repo Guide
You are working on the open-slide framework — the runtime, CLI, and tooling that ship to npm.
(Slide-authoring guidance lives in the slide-authoring / create-slide skills under apps/demo/.claude/skills/. Use those only when editing files inside apps/demo/slides/.)
Layout
pnpm + Turbo monorepo.
| Path | Package | Role |
|---|---|---|
packages/core |
@open-slide/core |
Runtime (viewer, present mode, inspector), Vite plugin, open-slide dev/build CLI. |
packages/cli |
@open-slide/cli |
npx @open-slide/cli init scaffolder + project template. |
apps/demo |
private | Local consumer of @open-slide/core via workspace:*. Dogfood target — run pnpm dev here to exercise the framework. |
apps/web |
private | Marketing site (Next.js). |
Shared config: biome.json, turbo.json, pnpm-workspace.yaml, tsconfig per package.
Workflow
pnpm dev # turbo: runs demo against local core
pnpm build # build all packages
pnpm typecheck # tsc across the graph
pnpm check # biome (format + lint + organize imports)
pnpm check:fix # auto-fix what biome can
pnpm test # vitest
Filter to one package: pnpm core <script> / pnpm cli <script>.
Hard rules
- Biome must pass before commit. Run
pnpm check(orpnpm check:fix). CI and the user's review both expect a clean tree. - If
packages/coreorpackages/clichanges, add a changeset. Runpnpm changeset, pick the right package(s) and bump (patchfor fixes/polish,minorfor new public API,majorfor breaking). Apps (demo,web) and root tooling do not need one. - Changeset descriptions: short and direct. One line, present-tense, what changed from a user's perspective. Match the tone of
.changeset/*.mdalready in the repo. No paragraphs, no rationale, no "this PR…".- Good:
Replace spinner with a hairline + sliding bar for slide and presenter loading states. - Bad:
This change introduces a new loading indicator because the previous spinner felt heavy and we wanted something more subtle for presentation contexts…
- Good:
- Don't bump versions or edit
CHANGELOG.mdby hand —changeset versionowns that. - Don't add dependencies casually. The
coreruntime ships to users; every dep inflates install size. packages/core/src/app/components/uiis shadcn-generated and biome-ignored — leave it alone unless regenerating.- Default to writing no comments. Only add one when the WHY is non-obvious — a hidden constraint, a subtle invariant, a workaround for a specific bug, behavior that would surprise a reader. Don't explain WHAT the code does (well-named identifiers handle that), don't reference tasks/PRs/callers ("added for X", "used by Y"), don't write section-divider banners (
// ── Section ──) or module-header descriptions, and don't leave commented-out code. If removing a comment wouldn't confuse a future reader, don't write it.
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.
- 1mo ago First seen · 48 lines · 789 tokens per session scan A 8a26685ba394
open-slide AGENTS.md is an instructions file published in the GitHub repository 1weiho/open-slide (9,292 stars, last pushed 7d ago), licensed MIT. It adds 789 tokens to every session, about $0.0032 per session on Opus 5.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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.