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 GCWing/Sparo-OS --skill presentation-directorgit clone --depth 1 https://github.com/GCWing/Sparo-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/gcwing/sparo-os/presentation-director)<a href="https://agentmods.dev/skills/gcwing/sparo-os/presentation-director"><img src="https://agentmods.dev/badge/skills/gcwing/sparo-os/presentation-director/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/gcwing/sparo-os/presentation-director"><img src="https://agentmods.dev/badge/skills/gcwing/sparo-os/presentation-director.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.00062 | $0.01344 |
| Opus 5.5 | $0.00025 | $0.00538 |
| Sonnet 5.5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
presentation-director 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Presentation Director
Workflow
- Start from the user's topic and optional materials. Infer audience, purpose, duration, page count, language, color direction, visual density, and evidence strategy. Ask only when an unknown materially changes the result.
- Research before writing. Separate verified evidence, attributed opinion, inference, and unsupported material. Never invent metrics, quotations, sources, product facts, or customer claims.
- Build the entire structured manuscript and speaker script in one pass, using stable
p01-style slideIds. Commit both withcommit_presentation_manuscript. The runtime validates the document, serializes canonicalmanuscript.mdandspeaker-script.md, and records the authoritative Manuscript revision. - Review the complete manuscript as one causal argument with
review_presentation_manuscript. Repair narrative roots, not isolated sentences. - Create a topic-specific PresentationSystem. Color and density are inferred design decisions, not mandatory user fields.
- Render one Design Case using three real pages from the frozen manuscript: opening/statement, evidence/process, and complex/closing. Never use placeholder copy.
- Call
confirm_design_casewith the three rendered page references and wait for the dedicated confirmation card. The user makes the single approve-or-revise decision; a multimodal model may inspect the renders and offer a recommendation but does not bypass this card. - Prepare grounded media, charts, diagrams, and semantic SVG assets required by the complete manuscript.
- Generate pages one by one with
generate_slide_visual, in Manuscript order and against the approved case revision. Independently author each page's content hierarchy and layout from the Manuscript; Runtime does not inject or string-match the copy. Retry only for an explicit deterministicRuleViolation. - After all pages exist, prepare and commit one deck-wide review with
review_deck. Compare every page against the complete Manuscript and speaker script, commit explicit alignment coverage, and use rendered evidence when multimodal; otherwise use the VisualInspectionBundle and report review coverage honestly. - Apply findings by root cause: manuscript, PresentationSystem, asset strategy, recipe family, or a bounded set of affected pages. Do not patch every page independently.
- Export only exact passed deck/system/review revisions.
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 · 74 lines · 62 tokens per session scan A ee59e19212fe
presentation-director is a skill published in the GitHub repository GCWing/Sparo-OS (25 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,344 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-08-30.
Other skills, from other repositories
apps
Build and iterate on schema-backed Swarm Apps with live models, named queries, custom actions, and json-render interfaces using the app-upsert, app-get, app-list, and app-patch tools.
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, files and bash over the agent-fs drive (ctx.fs…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
motion-design-video-analysis
Reverse-engineer a short motion-design / product-update video (animation technique, timing and easing, composition, transitions, likely tooling, vibe, audio) and produce a rebuild spec someone can build from. Default path is one call to google/gemini-3.8-flash over sampled frames, then a mandatory by-eye check of…
open-prompt-showreel
Make a design-led motion-graphics video (showreel, eval comparison, feature or bug-hunt story) from one open prompt. Claude Opus at max effort designs, codes and renders the whole thing itself in a scratch dir, with no template and no repo PR. Use for any "make a video for X" / "do a showreel for Y" / "a little…