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 joaoguirunas/team-os --skill presentation-designgit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/presentation-design)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/presentation-design"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/presentation-design/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/joaoguirunas/team-os/presentation-design"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/presentation-design.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.00050 | $0.02074 |
| Opus 5.5 | $0.00020 | $0.00830 |
| Sonnet 5.5 | $0.00010 | $0.00415 |
| Haiku 4.5 | $0.00005 | $0.00207 |
Grade A, and why
presentation-design 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 20d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Design Diagnostic
Purpose
Design and evaluate presentations that communicate effectively. Provides frameworks for planning, visual design, cognitive load management, and evaluation. Applicable to any presentation tool (reveal.js, PowerPoint, Keynote, Google Slides).
Core Principle
Audience-centered design. Every decision should serve audience understanding, not presenter convenience.
Quick Reference: Common Problems
| Problem | Symptom | Fix |
|---|---|---|
| Wall of Text | Slides are paragraphs | Assertion-evidence structure |
| Bullet Point Disease | Lists instead of visuals | One concept + visual evidence |
| Kitchen Sink | Everything included | Essential vs. expandable content |
| Pretty but Empty | Design without substance | Message-first design |
| Cognitive Overload | Too much per slide | One key concept per slide |
Phase 1: Audience & Content Planning
Key Questions
- Who specifically is my audience? What's their knowledge level?
- What's the ONE main message? What should they remember?
- What are 3-5 supporting points? How do they reinforce the message?
- What evidence supports each point? Visual, data, examples?
- What action should they take? What's the call to action?
- What are time constraints? What's essential vs. optional?
Actions
- Create audience persona(s)
- Write one-sentence main message
- Organize supporting points in logical flow
- Identify evidence for each point
- Define essential vs. expandable content
- Sketch presentation flow
Phase 2: Visual Strategy
Assertion-Evidence Structure
Replace bullet points with:
- Assertion: Clear, complete sentence stating the point
- Evidence: Visual that supports the assertion
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
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.
- 20d ago Changed · +2 lines eb0f672cf9ba
- 1mo ago First seen · 298 lines · 50 tokens per session scan A 00ea7fd7fb33
presentation-design is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 2,074 once invoked, about $0.0002 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-16.
Other skills, from other repositories
anatomy
Explain an idea as an interactive isometric machine figure.
canva
Create and edit Canva designs, generate images, remove backgrounds, recover editable layers, and work with Canva libraries. Use for branded presentations and slide decks, campaign artwork, flyers and banners, applying saved brand kits and templates, and resizing designs for social posts and stories through Canva's…
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
visual-artifact-design
A general workflow for creating, editing, diagnosing, or checking things people will see, read, or use. It defines the intended medium, audience, required outcome, evidence, and final consumer before work begins.
journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…
46-brand-guideline-global
Use when brand VISUAL rules have to be created or updated — brand personality, color system, typography, logo usage, imagery and visual tone, component rules, accessibility contrast, standard asset sizes, and file naming. It is the source document every design skill and the Brand Hub reads. Trigger on 'brand…