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/squadcodercom/squadcoder/open-slide-best-practicesnpx skills add squadcodercom/squadcoder --skill open-slide-best-practicesgit clone --depth 1 https://github.com/squadcodercom/squadcoderWrote 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/squadcodercom/squadcoder/open-slide-best-practices)<a href="https://agentmods.dev/skills/squadcodercom/squadcoder/open-slide-best-practices"><img src="https://agentmods.dev/badge/skills/squadcodercom/squadcoder/open-slide-best-practices.svg" alt="Measured on agentmods" 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 | $0.00179 | $0.03610 |
| Opus 5 | $0.00089 | $0.01805 |
| Sonnet 5 | $0.00036 | $0.00722 |
| Haiku 4.5 | $0.00018 | $0.00361 |
Grade A, and why
open-slide-best-practices 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
open-slide Best Practices for Israeli Developers
Adapted from 1weiho/open-slide (MIT). Hebrew and RTL adaptations by skills-il.
Problem
open-slide ships an opinionated authoring system: a fixed 1920×1080 React canvas, a typed DesignSystem const, a themes folder, an inspector that drops @slide-comment markers in source, and five built-in skills (slide-authoring, create-slide, create-theme, apply-comments, current-slide). None of those touch Hebrew or RTL. Out of the box, a deck written by a coding agent comes out left-aligned, system-font only, with paddingLeft that fights the Hebrew reading order, and no guidance for mixed Hebrew+English text. Israeli developers waste hours retrofitting RTL, loading Hebrew Google Fonts, and discovering that the type scale (140–200px hero) which works in Inter looks cramped in Heebo at the same weight.
Instructions
When to use
Use this skill whenever you are writing or editing code under slides/<id>/ in an open-slide project, creating a theme under themes/, or processing inspector comments — especially when any of that content is in Hebrew or bilingual.
New project setup
When in an empty folder or workspace with no existing open-slide project, scaffold one using:
npx @open-slide/cli init my-slide
cd my-slide
pnpm dev
Replace my-slide with a suitable project name. The scaffolder ships with the upstream agent skills preconfigured; this skill provides Hebrew and RTL adaptations on top.
Hebrew and RTL
For any Hebrew or bilingual deck, load ./rules/hebrew-rtl.md first. It covers:
- Hebrew Google Fonts (Heebo, Rubik, Assistant, Noto Sans Hebrew) with
subset=hebrew - The
<html dir="rtl">set-up vs per-pagedirattribute (the canvas root is the page component, not the document) - CSS logical properties (
paddingInlineStart,marginInlineStart,insetInlineStart) instead ofpaddingLeft/marginLeft/left flexDirection: 'row-reverse'vs settingdiron the flex container- Bidirectional text with
<bdi>for mixed Hebrew + Latin (brand names, code, URLs) - Hebrew-aware type scale tuning (Hebrew renders ~10–15% wider per character at the same px size)
- Hebrew
DesignSystem.fonts.displayandfonts.bodychoices that work at hero size - RTL-aware theme markdown patterns under
themes/ - Hebrew typography pitfalls: nikkud rendering, sofit letter spacing, hyphen vs maqaf
What ships with it
9 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.
- yesterday First seen · 154 lines · 179 tokens per session scan A 9cd6e0368972
open-slide-best-practices is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 179 tokens to every session and 3,610 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
React
ContextOS skill for modern React (v18/v19), component architecture, state colocation, render optimization, and Vercel performance rules.
react-patterns
Modern React patterns, hooks, and state management principles.
state-management
Client and server state management standards using Zustand and TanStack Query. Enforces minimal global state, optimistic updates, and clean query invalidation.
react-expert
Expert modern React (18/19): hooks, component design, state, performance, and Server Components. Trigger keywords: React, hooks, useState, useEffect, useMemo, useCallback, useRef, context, re-render, key, Suspense, Server Components, RSC, JSX, stale closure. Use when building/refactoring components or hooks, fixing…
scaffold
Greenfield or extend a Next.js app with Tailwind v4, tRPC, TanStack Query, optional Clerk, Neon/Drizzle, Vercel, and intake-selected add-ons (AI SDK, Resend, Stripe, Sentry, PostHog) fully installed and build-green. Use for /scaffold or new project setup.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.