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.
curl -O https://raw.githubusercontent.com/pandazki/pneuma-skills/main/.agents/skills/showcase/SKILL.mdgit clone --depth 1 https://github.com/pandazki/pneuma-skillsWrote 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/pandazki/pneuma-skills/showcase)<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.
<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>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.00031 | $0.01122 |
| Opus 5.5 | $0.00012 | $0.00449 |
| Sonnet 5.5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
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.
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 featuresmodes/<name>/skill/— what the mode does, its workflow, unique capabilitiesmodes/<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":
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.
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.
- 14d ago Changed 6eb51d75c634
- 1mo ago First seen · 97 lines · 31 tokens per session scan A 9de523556fae
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.
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…
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'…
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…
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…
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…
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…