pneuma-skills: Skill for Codex

.agents/skills/showcase/SKILL.md

showcase is a skill for Codex from pandazki/pneuma-skills. It costs 31 tokens per session (1,122 once invoked), scanned A, original, MIT.

A workflow for creating or refreshing showcase materials for a Pneuma mode. It produces launcher metadata, a hero image, and feature images based on the mode's documented capabilities.

In plain words
What is it for?
Creating or updating showcase metadata, taglines, highlights, hero artwork, and feature images.
Why use it?
It turns a mode's existing description and features into the materials needed for a gallery listing. It also keeps the showcase information in the mode's project files.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is pandazki/pneuma-skills's own configuration. It tells Codex how to work on pneuma-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pneuma-skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pandazki/pneuma-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pandazki/pneuma-skills/main/.agents/skills/showcase/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pandazki/pneuma-skills

Made for: Codex.

Wrote 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.

agentmods badge for showcase

README.md
[![agentmods](https://agentmods.dev/badge/skills/pandazki/pneuma-skills/showcase/github.svg)](https://agentmods.dev/skills/pandazki/pneuma-skills/showcase)
Your own site
<a href="https://agentmods.dev/skills/pandazki/pneuma-skills/showcase"><img src="https://agentmods.dev/badge/skills/pandazki/pneuma-skills/showcase/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.

agentmods 80×15 button for showcase

Your own site · 80×15
<a href="https://agentmods.dev/skills/pandazki/pneuma-skills/showcase"><img src="https://agentmods.dev/badge/skills/pandazki/pneuma-skills/showcase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,122 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.01122
Opus 5.5 $0.00012 $0.00449
Sonnet 5.5 $0.00006 $0.00224
Haiku 4.5 $0.00003 $0.00112

Measured 14d ago against content hash 6eb51d75c634, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

showcase 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 14d 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.

.agents/skills/showcase/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/showcase — Generate Mode Showcase Materials

Generate showcase marketing images and metadata for a Pneuma mode's launcher gallery.

Input

The user provides a mode name (e.g. remotion, draw). If not specified, ask.

Step 1: Analyze the Mode

Read the mode's manifest and skill to understand:

  • modes/<name>/manifest.ts — displayName, description, icon, key features
  • modes/<name>/skill/ — what the mode does, its workflow, unique capabilities
  • modes/<name>/showcase/showcase.json — existing showcase data (if any)

Identify 3 key selling points — the features that would make someone want to try this mode. Think from a user's perspective: what's exciting? what's unique?

Step 2: Write showcase.json

Create modes/<name>/showcase/showcase.json:

{
  "tagline": "Short punchy tagline (5-10 words)",
  "hero": "hero.png",
  "highlights": [
    {
      "title": "Feature Name",
      "description": "1-2 sentence description of the feature and why it matters.",
      "media": "feature-name.png",
      "mediaType": "image"
    }
  ]
}

Rules:

  • Tagline: short, evocative, no period at end
  • 3 highlights (occasionally 4 for complex modes)
  • Titles: 2-4 words, punchy, title case
  • Descriptions: concrete, benefit-focused, 1-2 sentences
  • Media filenames: kebab-case, descriptive

Step 3: Generate Showcase Images

Generate 4 images (1 hero + 3 highlights) using modes/_shared/scripts/generate_image.mjs through OpenRouter (OPENROUTER_API_KEY). New images default to GPT Image 2.5 Flare; pass --model sunburst when generation needs greater precision. Use edit_image.mjs for edits (Sunburst by default), or generate_image.mjs --model sunburst --image-urls ... for edits with multiple references. Inspect reference images first. If OpenRouter image generation is unavailable, complete the metadata and report which assets still need generation.

Image specs:

  • Dimensions: 1376×768 pixels (16:9)
  • Save to: modes/<name>/showcase/

Visual style — "Ethereal Tech Dark Mockup":

Read the full file on GitHub · 97 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 14d ago Changed 6eb51d75c634
  2. 1mo ago First seen · 97 lines · 31 tokens per session scan A 9de523556fae

Subscribe to this mod's changes

showcase is a skill published in the GitHub repository pandazki/pneuma-skills (161 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,122 once invoked, about $0.0001 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-09-11.

Related

Other skills, from other repositories

ralph

Launcher for the Ralph-style queue drain script - emits the right node ralph-loop.mjs invocation based on the user's filter and bounds. The actual loop runs as a Node script that opens one server run and spawns one claude -p --worktree per iteration under its own seat; this skill is the configurator, not the loop. Use…

jpicklyk/task-orchestrator · 108 tokens

session-retrospective

Analyzes the current implementation run - evaluates schema effectiveness, delegation alignment, note quality, and plan-to-execution fit. Captures cross-session trends and proposes improvements when patterns repeat. Use after implementation runs, or when user says 'retrospective', 'session review', 'what did we learn'…

jpicklyk/task-orchestrator · 106 tokens

adopt-project-scope

Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…

jpicklyk/task-orchestrator · 99 tokens

configure-server

Configures how the MCP Task Orchestrator SERVER runs and is reached — transport (HTTP vs STDIO), the REST API, port publishing, config mounts, and config-sync. Use when a user says: run the server, register the image, set up the Docker container, enable the REST API, set up config-sync, reconfigure the server, change…

jpicklyk/task-orchestrator · 159 tokens

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…

jpicklyk/task-orchestrator · 174 tokens

quick-start

Interactive onboarding for the MCP Task Orchestrator. Detects empty or populated workspaces and walks through how plan mode, persistent tracking, and the MCP work together. Use when a user says "get started", "how do I use this", "quick start", "first time setup", "onboard me", "what can this MCP do", or "help me…

jpicklyk/task-orchestrator · 82 tokens