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/librefang/librefang-registry/presentationnpx skills add librefang/librefang-registry --skill presentationgit clone --depth 1 https://github.com/librefang/librefang-registryWhat 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.00016 | $0.00664 |
| Opus 5 | $0.00008 | $0.00332 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
presentation 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 2d 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.
This is a copy
97% identical to presentation — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Expert
A communication strategist with extensive experience crafting executive presentations, technical talks, and pitch decks. This skill provides guidance for structuring narratives, designing visually clear slides, and delivering content that engages audiences, whether presenting to investors, engineering teams, or conference attendees.
Key Principles
- Start with the audience and their key question; every slide should advance toward answering what they need to know, decide, or do
- Follow the Minto Pyramid Principle: lead with the conclusion or recommendation, then support it with grouped arguments and evidence
- Apply the "one idea per slide" rule; if a slide requires more than one takeaway, split it into multiple slides with clear transitions
- Use visual hierarchy to guide attention: large text for key messages, smaller text for supporting detail, and whitespace to prevent cognitive overload
- Rehearse with a timer; knowing your material reduces filler words and ensures you respect the audience's time
Techniques
- Structure the deck with a clear arc: context (why we are here), problem (what is at stake), solution (what we propose), evidence (why it works), and call to action (what happens next)
- Apply the 30-point font rule as a minimum for body text; if text needs to be smaller to fit, there is too much content on the slide
- Use data visualizations instead of tables: bar charts for comparison, line charts for trends, pie charts only for 2-3 category proportions
- Write presenter notes for every slide with the key talking points and transition sentences to the next slide
- Use progressive disclosure: reveal complex diagrams or lists step by step using builds or animation sequences to maintain focus
- Design a consistent visual language: one primary font, one accent color, consistent alignment grids, and repeating layout templates
- Include a summary slide before the Q&A section that restates the three most important points from the presentation
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.
- 2d ago First seen · 43 lines · 16 tokens per session scan A 0fa03d43dbc4
presentation is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 8d ago), licensed MIT. It adds 16 tokens to every session and 664 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to presentation, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
Presentation Skills Index
Skills for creating presentations, slides, and visual documentation.
impress-presentations
Use when creating, opening, or editing LibreOffice Impress ODP presentations, or PPTX decks only when PowerPoint compatibility is explicitly required.
agent-loop
Production Claude agent loop — Session/Harness/Registry/Tool abstraction, DRYRUN safety guard, APScheduler integration, dead-letter error handling, tool registry, and observability hooks for autonomous agent systems.
notion
Notion API for creating and managing pages, databases, and blocks. Use when the user wants to create a Notion page, query a Notion database, update Notion properties, search Notion, add content to Notion, manage Notion blocks, or interact with Notion data sources and workspaces via the API.
agentic-supply-chain-detection
Detect agentic supply-chain risks: compromised dependencies, malicious plugins/tools/models, and untrusted update sources.
skill-vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.