Borrowing it
Nothing to install: this file belongs to adithya-s-k/research-presentation-template. 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/adithya-s-k/research-presentation-template/main/CLAUDE.mdgit clone --depth 1 https://github.com/adithya-s-k/research-presentation-templateWrote 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/adithya-s-k/research-presentation-template/claude-md)<a href="https://agentmods.dev/instructions/adithya-s-k/research-presentation-template/claude-md"><img src="https://agentmods.dev/badge/instructions/adithya-s-k/research-presentation-template/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.01420 | $0.01420 |
| Opus 5 | $0.00710 | $0.00710 |
| Sonnet 5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
Grade A, and why
research-presentation-template 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — authoring this deck
You are helping build a research talk. This repo is a fixed-canvas React deck: every slide is a component authored against a 1280×720 stage that scales to any projector. Read this before writing a slide.
AGENTS.md points here; both files describe the same rules.
The three things people get wrong
- Too much on one slide. A slide is one idea. If it needs a paragraph, it's
two slides. The
OverflowGuardwill scream (red badge, dev only) when content spills past the canvas — that's a design signal, not a bug to suppress by shrinking type. - Type too small. Body text ≥ 22px, bullets ~34px, slide titles ~46px, big claims 54–92px. The canvas is 1280 wide, so 22px here reads like 14pt in PowerPoint — from the back of a lecture hall that's already the floor.
- Editing the wrong file. Title, authors, venue, links, theme, social card:
all in
presentation.config.json. Never hard-code them in a slide.
Where things live
presentation.config.json the only file to edit per talk
src/config.ts typed view of it
src/themes/index.ts THEMES — token sets (dark + light per theme)
src/ThemeContext.tsx useTheme() -> { T, glow, mode, name }
src/deck/ Deck, SlideShell, PrintMode, Settings, Backdrop, OverflowGuard
src/primitives/ Panel Chip Bullet Accent Stat Figure Quote Rise Stagger CodeBlock
src/slides/ one file per slide + index.ts (the deck order)
scripts/export-deck.mjs PPTX + PDF capture
scripts/make_og.py social card
examples/ a real, complete talk you can run and copy from
Adding a slide
- Create
src/slides/NN_Name.tsxexporting one component. - Add one line to the
slidesarray insrc/slides/index.ts. - Section numbers derive themselves — never hard-code a kicker number. Set
bare: truefor title / divider / closing slides so they don't consume one.
A content slide is always SlideShell + absolutely-positioned content:
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 · 126 lines · 1,420 tokens per session scan A 44df3316c9e7
research-presentation-template CLAUDE.md is an instructions file published in the GitHub repository adithya-s-k/research-presentation-template (8 stars, last pushed 1mo ago), licensed MIT. It adds 1,420 tokens to every session, about $0.0071 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.