Orkas is a desktop application for commanding a team of AI agents through one chat, with a commander model assigning work to specialist agents in parallel or in sequence. People use it to coordinate research, writing, presentations, and software tasks while keeping files on their computer. The catalogue includes skills for extending the agents available to Orkas.
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 Orkas-AI/Orkas --skill ppt-plannergit clone --depth 1 https://github.com/Orkas-AI/OrkasWrote 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/orkas-ai/orkas/ppt-planner)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ppt-planner"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ppt-planner/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/orkas-ai/orkas/ppt-planner"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ppt-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 35 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- low Excessive Agency · line 158 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00003 | $0.03795 |
| Opus 5 | $0.00002 | $0.01898 |
| Sonnet 5 | $0.00001 | $0.00759 |
| Haiku 4.5 | $0.00000 | $0.00380 |
Grade A, and why
ppt-planner 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 10d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PPT Planner
Read only after ppt-router chooses CREATE or OUTLINE. Planning is the source of truth for construction, not optional prose around the deck.
1. Presentation brief
Lock these fields from the request and inspected materials:
- audience and decision, learning, sales, or communication job;
- desired audience action or takeaway;
- language, slide-count range, tone, and content density;
- source boundary: supplied-only, supplied-plus-current-research, or clearly labeled draft assumptions;
- must-include, must-avoid, confidentiality, brand, and template/reference constraints;
- delivery format and aspect ratio; default to editable
.pptxand 16:9 when unspecified.
When the user explicitly supplies slide titles, labels, or an ordered page list, record those visible strings and their order as a verbatim content contract. Do not improve, synonymize, shorten, or replace them with autonomous assertion titles. Assertion-title guidance applies only where the user did not fix the visible wording.
Ask only when a missing answer would change the deck's purpose, evidence boundary, or deliverable. Otherwise choose a sensible default and record it.
2. Visual source and references
Resolve one visual source before choosing an art direction:
autonomous: no visual reference exists. This is a normal, complete path. Do not ask the user to find a reference and do not reduce the deck to a generic title-and-bullets template. Derive a suitable visual character from the audience, communication job, subject matter, tone, and available evidence.text-direction: translate the user's words into a usable visual system without inventing a named brand or claiming an exact external style match.reference-image: inspect every supplied reference image and extract only the relevant visual signals: palette hierarchy, canvas/background treatment, typography character, grid and alignment, whitespace, dominant-object scale, image crop/focal point, surface treatment, and recurring motifs. Record uncertain inferences as low confidence. A reference image is not a reusable slide asset unless the user supplied or authorized it for reuse.reference-deck: decide whether the PPTX isinspirationor an authorizedtemplate-source. Inspect all source slides structurally. For strict template following, also render and inspect every source slide before mapping output roles to reusable source patterns; for inspiration, render enough slides to cover every recurring layout family and the opening/section/data/close roles. Extract theme colors, font evidence, margins, alignment lines, background language, image treatment, chart/table treatment, recurring furniture, and slide-role patterns.existing-deck: preserve its current visual system unless the user authorizes a bounded redesign.
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.
- 10d ago First seen · 261 lines · 3 tokens per session scan A c79ceb668b25
ppt-planner is a skill published in the GitHub repository Orkas-AI/Orkas (1,808 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 3,795 once invoked, about $0.0000 per session on Opus 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
tutti-workspace-app-factory
Create, convert, or repair one Tutti workspace app as either a self-contained publishable package under package/ or a Chrome-style local debug app under .tutti/dev-app/. Use for mention://workspace-app-factory/create handoffs, mention://workspace-app-factory handoffs, standalone app generation, adapting existing…
tutti-ui-system
Use when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business components, or maintaining UI-system storyboard inventory.
tutti-agent-workspace-app
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging…
takt
A workflow engine that runs a task through a sequence of steps defined in a YAML file, using separate coding agents for the work.
takt
A workflow engine for coordinating multiple coding agents. It reads a YAML workflow, a text configuration format, and moves agents through its defined steps and rules.
create-coordclaw-team
A Skill for creating a CoordClaw multi-agent collaborative team. Through an 8-step standardized process, from requirement gathering to team validation, rapidly build a complete AI team.