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 Avinava/document-design-system --skill presentation-designgit clone --depth 1 https://github.com/Avinava/document-design-systemWrote 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/avinava/document-design-system/presentation-design)<a href="https://agentmods.dev/skills/avinava/document-design-system/presentation-design"><img src="https://agentmods.dev/badge/skills/avinava/document-design-system/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/avinava/document-design-system/presentation-design"><img src="https://agentmods.dev/badge/skills/avinava/document-design-system/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.00126 | $0.01766 |
| Opus 5.5 | $0.00050 | $0.00706 |
| Sonnet 5.5 | $0.00025 | $0.00353 |
| Haiku 4.5 | $0.00013 | $0.00177 |
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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Design
A slide is seen for as long as it takes to say one thing. That constraint drives every rule here.
A deck is not a document with page breaks. If the content only makes sense when read closely, it is a document — say so and use analytical-document-design or writing-documents instead. Converting a document into slides by cutting it into pieces produces a deck that is bad to present and worse to read.
One idea per slide
The title states the idea as a claim, not a topic. Everything else on the slide supports that claim.
- "Ingestion is our concentration risk" — a claim. The audience knows what to look for.
- "Ingestion metrics" — a topic. The audience has to work out what they are meant to conclude.
If a slide needs two titles, it is two slides. Slides are free; attention is not.
Reading and presenting are different jobs
Decide which deck this is, because the answer changes the design and you cannot have both in one artifact:
Presented — you are speaking over it. Slides carry few words, large type, and one visual. The detail lives in what you say.
Read (sent, not presented) — nobody narrates it. Slides need enough text to stand alone, which means more words and smaller type, and the deck is longer.
When both are needed, build the presented deck and pair it with a document, or add a speaker-notes block that prints but does not project. Do not compromise into a deck that is too dense to present and too sparse to read alone — the common failure that produces a wall of bullets nobody can use for either purpose.
Slide types
Use a small set. A deck where every slide has a different layout reads as a collection of unrelated files.
| Type | Use |
|---|---|
| Title | Deck title, presenter, date, context |
| Section divider | Marks a shift; a few words on an accent field |
| Statement | One sentence at large size. The argument's turning points |
| Metric | One to three numbers with labels and their denominators |
| Chart | One chart, one takeaway title |
| Diagram | One diagram, one takeaway title |
| Comparison | Two or three columns on a consistent set of criteria |
| Table | Small tables only — six rows and four columns is the practical ceiling |
| Agenda / summary | Structural orientation |
| Closing | The ask, the decision needed, or next steps |
What ships with it
16 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.
- core/a11y.md 2.9 KB
- core/base.css 7.5 KB
- core/print.css 4.3 KB
- core/themes/brand-template.css 4.1 KB
- core/themes/console-violet.css 3.5 KB
- core/themes/editorial-coral.css 1.3 KB
- core/themes/executive-navy.css 1.0 KB
- core/themes/field-notes.css 1.0 KB
- core/themes/horizon.css 1.9 KB
- core/tokens.md 8.6 KB
- references/deck-structure.md 3.3 KB
- references/slide-types.md 5.4 KB
- scripts/build_document.py 2.7 KB runs code
- scripts/export_pdf.mjs 4.2 KB runs code
- scripts/inline_fonts.py 4.3 KB runs code
- templates/deck.html 21 KB
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.
- 9d ago Changed · -2 lines 5b12821f5f41
- 1mo ago First seen · 139 lines · 126 tokens per session scan A fc8b15bf26ab
presentation-design is a skill published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 10d ago), licensed MIT. It adds 126 tokens to every session and 1,766 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
ui-ux-audit
Audits web UI and raises it from competent to exceptional. Catches what AI tools ship and people notice at once: broken or shifting layouts, cards and values off a shared line, orphaned words and lone grid items, drifting radii, gutters, ratios and component sizes, text overflow, missing states, poor contrast, small…
ui-ux-laws
Priority-ordered rulebook of core UX/UI laws, cognitive-psychology principles, Nielsen's usability heuristics, and accessibility requirements that Claude must actively apply (not just cite) whenever it designs, builds, redesigns, reviews, or critiques any user interface — websites, web/mobile apps, dashboards, forms…
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
design-component
Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, token mapping, and accessibility. Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework…
design-screen
Design or build a page, screen, landing page, website, app or UI from a request - the whole job, end to end. Use this for "design a landing page", "build a settings screen", "make me a website", "design the onboarding", "ออกแบบหน้าเว็บ", "ทำหน้า landing", "ออกแบบ UI", "ทำแอป". It runs the pipeline no single skill…
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.