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 instructions/byungjunjang/slide-master/claude-mdgit clone --depth 1 https://github.com/byungjunjang/slide-masterWrote 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/byungjunjang/slide-master/claude-md)<a href="https://agentmods.dev/instructions/byungjunjang/slide-master/claude-md"><img src="https://agentmods.dev/badge/instructions/byungjunjang/slide-master/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.01749 | $0.01749 |
| Opus 5 | $0.00874 | $0.00874 |
| Sonnet 5 | $0.00350 | $0.00350 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
slide-master 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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file is the project entry point for Claude Code. The ppt-master skill lives at .claude/skills/ppt-master/ and is auto-discovered by Claude Code.
Cross-harness (dual-host):
AGENTS.mdis the Codex-side execution-rules layer — it references this file as SSOT and only adds enforcement, so content edits here do not need mirroring there..codex/skills/holds generated Codex discovery stubs: after editing any.claude/skills/<name>/SKILL.mdfrontmatter, runpython3 .claude/skills/ppt-master/scripts/sync_codex_stubs.py(never hand-edit stubs;preflight.pyfails while they are stale). Skill content itself lives only in.claude/skills/.
Route before full-load (mandatory): for a presentation request, first read
.claude/skills/ppt-master/workflows/routing.md.
Select the route there, then read only the selected execution owner(s) in full.
Do not preload the main SVG skill for a direct-PPTX route. For a repository edit,
read the owner of the contract being changed; the main skill is authoritative only
for the main SVG family and the shared SVG steps that explicitly invoke it.
Project Overview
PPT Master is a presentation workflow package with SVG-authoring and direct-PPTX route families. The main SVG family uses Strategist → Image_Generator → Executor to convert source documents into editable DrawingML. Direct-PPTX routes preserve an existing PowerPoint package and use their own execution gates.
Main SVG Pipeline: Source Document → Create Project → [Template] → Strategist confirmation stage → [Image_Generator] → Executor Live Preview → Quality Check → Post-processing → Export PPTX
Route selection authority:
.claude/skills/ppt-master/workflows/routing.md
owns the complete matrix and wins over every summary below.
| Selected family | Full execution owner(s) |
|---|---|
| New SVG-authored deck or PPTX re-architecture | Main ppt-master/SKILL.md |
| Existing PPTX, strict 1:1 wording/page preservation with visual redesign | beautify-pptx.md, then the main skill only at its explicit shared-SVG handoff |
| Raw PPTX template plus new material/topic | ppt-template-fill/SKILL.md only |
| Finished PPTX, stable visible content/layout, add notes/audio/timing/transitions | native-enhance-pptx/SKILL.md, then its required execution workflow |
| Reusable template creation or another standalone workflow | The selected workflow; load another owner only at an explicit handoff |
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.
- 6d ago First seen · 95 lines · 1,749 tokens per session scan A c1f1b00bee9c
slide-master CLAUDE.md is an instructions file published in the GitHub repository byungjunjang/slide-master (229 stars, last pushed 1mo ago), licensed MIT. It adds 1,749 tokens to every session, about $0.0087 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-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).
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 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).
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.
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.
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.