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 SlideSpeak/slide-design-skill --skill opexgit clone --depth 1 https://github.com/SlideSpeak/slide-design-skillWrote 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/slidespeak/slide-design-skill/opex)<a href="https://agentmods.dev/skills/slidespeak/slide-design-skill/opex"><img src="https://agentmods.dev/badge/skills/slidespeak/slide-design-skill/opex/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/slidespeak/slide-design-skill/opex"><img src="https://agentmods.dev/badge/skills/slidespeak/slide-design-skill/opex.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.00084 | $0.00869 |
| Opus 5.5 | $0.00034 | $0.00348 |
| Sonnet 5.5 | $0.00017 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
opex 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 1mo 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.
What it actually says
Operational Excellence — Authoring Guide
A deliberately conservative internal management deck at the bar of a large industrial group's board and steering-committee communication. It is structured, dense and functional. It should look like something a real corporation would table in a programme review, not a designed artefact.
Action titles, not topics
Every content slide's title is a complete-sentence claim, never a label. Read top to bottom, the titles alone carry the management argument.
- Wrong: "Current situation"
- Right: "Growth through acquisitions has increased operational complexity."
Density is the point
These slides carry a lot, on purpose. Use the richest layout the content needs — a numbered point grid, a stat grid, a three-column table, a scoring matrix, a risk table, a layered architecture, an org hierarchy, a timeline. Type always stays readable (14–19px body); never shrink text to fit. Avoid large empty hero slides and excessive whitespace; a steering-committee slide is expected to be full.
Colour discipline
- White ground on content slides; deep navy (#15263D) on cover, closing, message bands and the governance rail.
- Corporate blue (#1F4E79) is the single accent: numerals, key markers, table emphasis, the recommended column. Steel blue (#4A77A8) is a tint only.
- The severity reds/ambers/greens exist only as risk-matrix likelihood/impact chips. Nowhere else.
- Hairlines (#D4DAE1) for rules, gridlines and table borders.
Imagery
- Charts, tables and diagrams are drawn by the system in its own hairlines.
- Any real-world photograph (a plant, a line, a logistics yard, a meeting) is a labelled placeholder frame, never an AI or stock image dropped onto a content slide.
Voice
- Lead with the conclusion. Plain, measured, corporate. No hype, no hedging.
- Sentence case everywhere. This is internal communication, not marketing.
- If a slide could appear in a consumer product launch, it is wrong for this deck.
What ships with it
5 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.
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.
- 1mo ago First seen · 46 lines · 84 tokens per session scan A 9b3c5bb5eb48
opex is a skill published in the GitHub repository SlideSpeak/slide-design-skill (29 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 869 once invoked, about $0.0003 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-30.
Other skills, from other repositories
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
queues-jobs
Implement reliable asynchronous jobs and message consumers with explicit delivery, retry and shutdown semantics. Use when adding BullMQ or another established queue, background processing or scheduled work; enqueue success is not job completion.