Borrowing it
Nothing to install: this file belongs to Chrisissorry/lazyslides. 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/Chrisissorry/lazyslides/develop/CLAUDE.mdgit clone --depth 1 https://github.com/Chrisissorry/lazyslidesWrote 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/chrisissorry/lazyslides/claude-md)<a href="https://agentmods.dev/instructions/chrisissorry/lazyslides/claude-md"><img src="https://agentmods.dev/badge/instructions/chrisissorry/lazyslides/claude-md.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.1 | $0.04714 | $0.04714 |
| Opus 5 | $0.02357 | $0.02357 |
| Sonnet 5 | $0.00943 | $0.00943 |
| Haiku 4.5 | $0.00471 | $0.00471 |
Grade A, and why
lazyslides CLAUDE.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 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.
How it starts
The opening of the file, as written. The whole thing — 502 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
LazySlides turns structured YAML into professional slide decks. Presentations are authored in YAML, rendered through Nunjucks templates into Reveal.js, and styled with Tailwind CSS 4.x. Distributed as an npm package (lazyslides) with an Eleventy plugin and CLI.
Presentation Authoring Workflow
Creating a new presentation
- Start with an outline — fill in
presentations/_template/outline.mdor use/create-outline - Run
/new-presentation— the slash command guides you through the full process - Or manually: create
presentations/{name}/index.mdwith YAML frontmatter
Adding slides
- Run
/add-slide— picks template, gathers content, inserts at the right position - Or manually: add a new
- template: ...entry to theslides:array
Editing slides
- Read the presentation's
index.md - Modify the YAML for the target slide
- Run
pnpm run validateto verify - Run
pnpm run devto preview
Validating
pnpm run validate # check all presentations
pnpm run renumber # update slide comment numbers
YAML Schema Reference
All presentations use this structure:
---
title: Deck Title # required
description: Subtitle
author: Speaker Name
theme: default # LazySlides theme name
transition: slide # global transition: none, fade, slide, convex, concave, zoom
progress: true
slideNumber: true
show_footer: true # show footer on slides (default: true, set false to hide globally)
math: true # enable KaTeX math rendering (opt-in)
slides: # required — array of slide objects
- template: content # required on every slide
title: Slide Title
# ... template-specific fields
hide_footer: true # optional — hide footer on this slide (default: false)
notes: | # optional speaker notes (all templates)
What to say during this slide
---
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 · 502 lines · 4,714 tokens per session scan A d474347abd7e
lazyslides CLAUDE.md is an instructions file published in the GitHub repository Chrisissorry/lazyslides (5 stars, last pushed 2mo ago), licensed MIT. It adds 4,714 tokens to every session, about $0.0236 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-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.