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/jayrha/agentskills/presentation-buildernpx skills add JayRHa/AgentSkills --skill presentation-buildergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWhat 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.00110 | $0.01742 |
| Opus 5 | $0.00055 | $0.00871 |
| Sonnet 5 | $0.00022 | $0.00348 |
| Haiku 4.5 | $0.00011 | $0.00174 |
Grade A, and why
presentation-builder 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Builder
Overview
This skill turns a topic, document, or rough idea into a tight, persuasive presentation outline. It enforces three rules that separate good decks from forgettable ones:
- One core message — the whole deck exists to make ONE point land.
- A narrative arc — slides progress like a story (tension → resolution), not a list of facts.
- One idea per slide — each slide advances the argument by exactly one step, with spoken-word speaker notes.
Keywords: presentation, slide deck, slides, pitch deck, keynote, talk, lecture, demo, storytelling, narrative arc, speaker notes, outline, slide outline, deck structure, conference talk, sales pitch.
The output is a structured outline (slide-by-slide), NOT a visually rendered deck. Hand the outline to PowerPoint, Google Slides, Keynote, or a tool like Marp/reveal.js.
When to use vs. not use
- USE for: structuring a new deck, converting a document/report into slides, reordering a rambling deck, writing speaker notes, sharpening a pitch.
- DON'T over-engineer for: a single status slide, or when the user already has a finished deck and only wants visual styling (that's a design task, not a structure task).
Workflow
Follow these steps in order. Do not skip the discovery step — a deck built without knowing the audience and the ask is the #1 cause of bad presentations.
Step 1 — Discover the four anchors
Before writing any slide, establish (ask the user if unknown, max 3-4 crisp questions):
| Anchor | Question to answer |
|---|---|
| Audience | Who is in the room? What do they already know, care about, and fear? |
| Goal / Ask | What should they DO or DECIDE after the talk? (One verb.) |
| Core message | The single sentence they should remember tomorrow. |
| Constraints | Time limit, slide count, format (live/async), tone. |
If the user gave a document, infer drafts of these from it, then confirm the core message before proceeding.
What ships with it
5 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 · 124 lines · 110 tokens per session scan A 2f0f86d77067
presentation-builder is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,742 once invoked, about $0.0006 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 skills, from other repositories
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
interpreting-mod-author-instructions
Use when deciding how to correctly download/install a Bethesda mod per the author's instructions — triggers "how do I install", "FOMOD choices", "which file to download", "author说明", "install instructions", "which variant", "按作者说明安装", "这个mod怎么装". NOT for deciding whether to include the mod (use evaluating-bgs-mods)…
using-bgs-archive
Use when the user wants to inspect, list, extract, unpack, or repack Bethesda BA2/BSA archives; determine archive format/version/compression; or build archive assets for an MO2 overlay. Triggers - "unpack BA2", "extract BSA", "pack archive", "inspect archive", "bgs-archive".
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.
design-director
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.