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 skills add KhaledSaeed18/dotclaude --skill presentation-outlinegit clone --depth 1 https://github.com/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/presentation-outline)<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/presentation-outline"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/presentation-outline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/khaledsaeed18/dotclaude/presentation-outline"><img src="https://agentmods.dev/badge/skills/khaledsaeed18/dotclaude/presentation-outline.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.00880 |
| Opus 5.5 | $0.00042 | $0.00352 |
| Sonnet 5.5 | $0.00021 | $0.00176 |
| Haiku 4.5 | $0.00010 | $0.00088 |
Grade A, and why
presentation-outline 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 25d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A presentation is an argument with a time limit. The audience remembers one message and two or three supporting points; everything else is either evidence for those or noise. Build the outline from the message down, then fit it to the minutes.
Step 1: the message
One sentence the audience should repeat afterwards. For a defence: the contribution and what supports it ("A citation-verification hook cuts fabricated references in AI-assisted drafts to zero in our study, and here is how we know"). For a status talk: the state and the ask. Write it first; every slide either supports it or goes.
Step 2: audience and occasion
- What they know (skip it), what they doubt (address it), what they want (lead with it).
- Slot length, including questions. Plan for 70% of the slot; talks run long.
- Rule of thumb: one slide per one to two minutes; a 20-minute talk has 10 to 15 slides.
Step 3: structure
Defence or research talk (20 to 40 min):
- Title, name, one line of context.
- The problem and why it matters (one concrete example, one number).
- The gap and the research questions (verbatim from the thesis).
- Approach in one diagram.
- Method essentials (what an examiner needs to trust the results; details in backup slides).
- Results: one slide per research question, claim in the title, one figure or table.
- Limitations, stated plainly.
- Contributions and what they mean.
- Future work (concrete next studies).
- Thank you and the message restated. Then backup slides for questions.
Team or status talk (10 to 15 min): state, evidence, risks, ask, next steps.
Demo: what you will show and why it matters; the demo, scripted with a fallback recording; what was hard; what is next.
Step 4: slide by slide
Each slide gets:
- Title as the claim ("Variant B halves latency at every input size"), not a topic ("Results").
- One visual or three bullets, not both; a figure from
research-figuresat slide resolution, direct-labelled. - Speaker note: the two to four sentences said on the slide, in speaking voice; the transition to the next slide.
- Time: minutes allotted.
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.
- 25d ago First seen · 78 lines · 104 tokens per session scan A b8fb1cff5240
presentation-outline is a skill published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 2d ago), licensed MIT. It adds 104 tokens to every session and 880 once invoked, about $0.0004 per session on Opus 5.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-09-22.
Other skills, from other repositories
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
interactive-product-tour
Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of…
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
meta-prompt
Meta-prompting framework for critiquing responses, analyzing solution trajectories, and evaluating AI-generated content quality.
debate-simulator
Spin up 2-3 expert personas to debate any topic from different angles. Structure: Opening statements, rebuttals, cross-examination, closing arguments.
sports-trivia-builder
Generate sports trivia questions by sport/era/difficulty. Multiple formats with obscure stats, fun facts, pub quiz ready content.