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 wunki/dotfiles --skill workera-slidesgit clone --depth 1 https://github.com/wunki/dotfilesWrote 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/wunki/dotfiles/workera-slides)<a href="https://agentmods.dev/skills/wunki/dotfiles/workera-slides"><img src="https://agentmods.dev/badge/skills/wunki/dotfiles/workera-slides/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/wunki/dotfiles/workera-slides"><img src="https://agentmods.dev/badge/skills/wunki/dotfiles/workera-slides.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.00129 | $0.01188 |
| Opus 5.5 | $0.00052 | $0.00475 |
| Sonnet 5.5 | $0.00026 | $0.00238 |
| Haiku 4.5 | $0.00013 | $0.00119 |
Grade A, and why
workera-slides 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 15d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workera Slides Skill
Produces polished, on-brand Workera PowerPoint (.pptx) decks efficiently. Prioritizes visual clarity, Workera brand consistency, and concise messaging.
Mandatory Pre-Flight (do this every time, no exceptions)
- Read the PPTX skill at
/mnt/skills/public/pptx/SKILL.mdbefore writing any code. - Read the Workera Template PDF at
/mnt/project/TEMPLATE_Workera_Slides_Template_2025.pdf— it contains 100+ slides. Identify the best-matching layouts for the current request. Do NOT use every slide; curate only the most relevant patterns. - Extract exact hex codes, font names, and layout logic from the template. Never approximate.
Brand Rules
| Element | Guidance |
|---|---|
| Backgrounds | Deep plum for section dividers and title slides; cream/off-white for content slides |
| Accent colors | Magenta and orange — use for emphasis, icons, key data points |
| Typography | Bold sans-serif headers; clean body text; match weights exactly from template |
| Logo placement | Follow template positioning — typically top-left or bottom-right corner |
| Visual style | High contrast, dramatic, strong hierarchy — NOT generic corporate |
Match hex codes, font choices, and heading styles exactly as shown in the template. Flag any color or font decision that can't be directly confirmed from the template.
Design Principles
- Minimal text per slide — one strong idea per slide, supported by visuals or icons
- Bold headers — the header should communicate the point, not just label the slide
- Visual hierarchy first — size, color, and whitespace do the heavy lifting
- Character welcome — humor and personality are on-brand when context allows
- Icons and visuals — prefer over bullet lists wherever possible
Workflow
Step 1 — Scope the deck
- Parse the user's request to determine slide count, purpose, and audience.
- For decks 8 slides or more: confirm the proposed outline with the user before building.
- For decks under 8 slides: proceed, but briefly state the structure you're using.
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.
- 15d ago First seen · 120 lines · 129 tokens per session scan A 5d8daac25e27
workera-slides is a skill published in the GitHub repository wunki/dotfiles (47 stars, last pushed 10d ago), licensed MIT. It adds 129 tokens to every session and 1,188 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-10-02.
Other skills, from other repositories
manage-theme
Switch, create, or debug the color theme of a machine set up by urmzd/dotfiles: one theme colors Ghostty, Neovim (colorscheme and lualine), tmux (catppuccin flavour and colors), and the dotfiles' own output. Covers dotfiles theme / dotfiles theme set, writing a themes/ .toml or a pack's theme.toml, and per-shell…
style-brand
Frame and document a project's visual identity: terminal theme, font, demo capture pipeline, asset conventions. Use when establishing or maintaining brand consistency. Ships an example brand (Cyberdream + MonaspiceNe + teasr) as a template, not a mandate.
mcp-notion-usage-guide
A usage guide for connecting AI agents to Notion databases through MCP. Notion is a workspace for documents and databases, while a database view is a saved way of displaying database records.
assess-quality
Foundational quality framework: the five questions (readable, easy to start, expands without bloat, consistent, intentional) every other dev skill is judged against, plus the dual-audience and workshop principles. Use when onboarding to a project, defining a quality bar, setting an assessment checklist, or arbitrating…
create-oss-skill
Create well-formed Agent Skills following the agentskills.io specification. Scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
orchestrate-agents
Orchestrate multiple agent CLIs (Claude, Codex, Antigravity) via tmux with a shared fleet store, dispatching one guardian subagent per pane. Survey-first: inspects and adopts existing tmux sessions, windows, and agent panes before creating anything new. Use when running a multi-agent session, dispatching parallel…