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/aaronvanston/skills-presentations/presentation-contentnpx skills add aaronvanston/skills-presentations --skill presentation-contentgit clone --depth 1 https://github.com/aaronvanston/skills-presentationsWrote 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/skills/aaronvanston/skills-presentations/presentation-content)<a href="https://agentmods.dev/skills/aaronvanston/skills-presentations/presentation-content"><img src="https://agentmods.dev/badge/skills/aaronvanston/skills-presentations/presentation-content.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.00064 | $0.01135 |
| Opus 5 | $0.00032 | $0.00567 |
| Sonnet 5 | $0.00013 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
presentation-content 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Content
Write slide content that is bold, minimal, and designed for speaking to — not reading from.
Writing Principles
- Headlines that land — statements, not descriptions. "AI has no memory" not "Discussion of AI context limitations"
- Minimal text — if it takes more than 5 seconds to read, cut it
- Emphasis through scale — big words at light weight, not small words in bold
- Conversation starters — each slide prompts what you'll say, not what the audience reads
Headline Patterns
Statement headlines
Bold declarations that take a position:
- "Speed is a feature"
- "AI has no memory"
- "Context is everything"
- "Passive beats active"
Question headlines
Create tension and invite reflection:
- "What would we do differently if we started today?"
- "What does this mean for you?"
- "So does any of this actually work?"
Action headlines
Drive toward outcomes:
- "Building blocks over modules"
- "Always be gardening"
- "Let agents write their own rules"
Framing headlines
Set context for what follows:
- "How we got here"
- "Where we're going"
- "The real results"
Body Text Patterns
Bold lead-in + explanation
**Retention is the real metric**
Acquisition gets attention, but retention builds the business.
**Speed compounds**
Ship fast, learn fast, win fast — momentum is the moat.
Key phrase emphasis
Highlight critical words within sentences:
- "Give the right people, the right amount of information, at the right time"
- "We don't compete on features — we compete on speed and focus"
Minimal bullets
3-4 points maximum, each earning its place:
- Focus over breadth — Do one thing better than anyone.
- Platform, not tool — Customers run their whole operation here.
- Speed is the moat — Ship weekly, learn daily, compound forever.
Inline code
Use backticks for technical terms, file names, and commands within slides:
- "Start with
AGENTS.mdin your project root" - "Run
npx skills addto install"
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 · 164 lines · 64 tokens per session scan A e3b2ed97db43
presentation-content is a skill published in the GitHub repository aaronvanston/skills-presentations (10 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,135 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…