slide-sage: Instructions file for Codex

AGENTS.md

slide-sage AGENTS.md is an instructions file for Codex, OpenCode from rhnfzl/slide-sage. It costs 1,222 tokens per session, scanned A, original, MIT.

Instructions for Slide Sage, a tool that creates interactive HTML presentation files. It supports charts, diagrams, code examples, accessible color choices, and presentation controls.

In plain words
What is it for?
Use it to create slides, convert PowerPoint or PDF material, or improve an existing HTML presentation.
Why use it?
It provides a defined process for turning a presentation idea, PowerPoint, or PDF into a browsable slide deck.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

This is rhnfzl/slide-sage's own configuration. It tells Codex and OpenCode how to work on slide-sage itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything slide-sage configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rhnfzl/slide-sage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rhnfzl/slide-sage/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rhnfzl/slide-sage

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for slide-sage AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rhnfzl/slide-sage/agents-md.svg)](https://agentmods.dev/instructions/rhnfzl/slide-sage/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rhnfzl/slide-sage/agents-md"><img src="https://agentmods.dev/badge/instructions/rhnfzl/slide-sage/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,222 This file is loaded in full into every session.
When invoked 1,222 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01222 $0.01222
Opus 5 $0.00611 $0.00611
Sonnet 5 $0.00244 $0.00244
Haiku 4.5 $0.00122 $0.00122

Measured 6d ago against content hash 022b426afe2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

slide-sage 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 6d 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.

AGENTS.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slide Sage - AI Presentation Skill

Cross-platform instructions for AI coding tools (Claude Code, Codex CLI, Gemini CLI, Cursor, Copilot)

When a user asks to create a presentation, build slides, convert a PowerPoint or PDF, or make a slide deck, follow these instructions.

Quick Start

  1. Read skills/slide-sage/SKILL.md for the full workflow
  2. Read only the reference files you need from skills/slide-sage/references/
  3. Generate a single HTML file with inline CSS/JS
  4. All chart/diagram libraries loaded from CDN

What This Skill Does

Creates data-rich, interactive HTML presentations as single files. Specializes in:

  • Data visualization (Chart.js, ECharts, D3.js charts)
  • Architecture diagrams (CSS/HTML diagrams, SVG templates, inline SVG)
  • Code slides with syntax highlighting (Prism.js)
  • Professional styling with colorblind-safe palettes
  • Keyboard navigation, touch support, presenter mode

Workflow

  1. Detect mode: New presentation / PPT/PDF conversion / enhancement of existing HTML
  2. Gap-driven intake: Apply the intake rule below before generating
  3. Content analysis: Identify what libraries are needed (charts? diagrams? code?)
  4. Read relevant references: Only load the reference files needed for this presentation
  5. Generate: Single HTML file with all CSS/JS inline, libraries from CDN
  6. Deliver: Save file, mention how to open (browser) and export (Print > Save as PDF)

Intake rule

Infer audience and style from a detailed prompt and state the choice in one line. Ask only when the prompt is genuinely thin. Never block in one-shot, subagent, or CI runs: choose sensible defaults and state them in one line. Offer a visual preview only when style is unspecified and a browser is available.

When an interactive response would materially change the deck, ask one focused question. The visual preview is optional and must not delay generation.

Reader and density (ask when the prompt does not say)

Two answers decide whether a deck lands, and neither can be inferred from the audience. A leadership deck can be diagram-led or text-rich; the same deck can be presented or forwarded. A prompt almost never states either, so both are usually genuine gaps.

Read the full file on GitHub · 84 lines

Changes

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.

  1. 6d ago First seen · 84 lines · 1,222 tokens per session scan A 022b426afe2f

Subscribe to this mod's changes

slide-sage AGENTS.md is an instructions file published in the GitHub repository rhnfzl/slide-sage (3 stars, last pushed 1mo ago), licensed MIT. It adds 1,222 tokens to every session, about $0.0061 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.

Related

Other instructions, from other repositories

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens