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 FlorianBruniaux/claude-code-plugins --skill orchestratorgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/orchestrator)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/orchestrator"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/orchestrator/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/florianbruniaux/claude-code-plugins/orchestrator"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Data Exfiltration · line 44 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00066 | $0.01537 |
| Opus 5.5 | $0.00026 | $0.00615 |
| Sonnet 5.5 | $0.00013 | $0.00307 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
talk-pipeline 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 yesterday.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Talk pipeline orchestrator
Orchestrates the complete talk preparation pipeline from raw material to revision sheets. Can run the full pipeline or a single isolated stage.
Modes
--rex: REX talk with git/code proof (changelog, commits, measured metrics)--concept: Conceptual talk from article, ideas, notes (skips Stage 2)
Usage
/talk-pipeline # full pipeline, asks for context
/talk-pipeline --stage=extract # run a single isolated stage
/talk-pipeline --rex # REX mode (git archaeology included)
/talk-pipeline --concept # Concept mode (skip research)
/talk-pipeline --rex --slug=my-talk --event="Conf 2026" --date=2026-06-15 --duration=30
Context collection
Ask with AskUserQuestion if not provided:
- slug : kebab-case identifier (e.g., my-talk-topic)
- event : event name (e.g., Conf 2026, Tech Meetup)
- date : talk date (YYYY-MM-DD)
- duration : duration in minutes (e.g., 30)
- audience : audience profile (e.g., senior devs, tech leads, non-tech)
- type : --rex or --concept
- source_path : path to source material (article .mdx, transcript .md, notes)
- repo_path : (REX only) path to git repository for archaeology
Workflow
- Collect context using AskUserQuestion for required metadata
- Route by mode (
--rexvs--concept, skip Stage 2 if concept) - Run Stage 1 (
/talk-stage1-extract, always first) - Run Stages 2-4 in parallel (after Stage 1 confirmed)
- REX: extract -> research + concepts + position (in parallel)
- Concept: extract -> concepts + position (in parallel, skip research)
- CHECKPOINT: wait for angle + title choice (Stage 4 output)
- Run Stage 5 (
/talk-stage5-scriptwith validated choice) - Run Stage 6 (
/talk-stage6-revision) - Final summary: list all generated files with their paths
Dependency graph
extract (Stage 1)
|
+----------+-----------+
v v v
research concepts position
(Stage 2) (Stage 3) (Stage 4)
[--rex only] [CHECKPOINT]
| | |
+----------+-----------+
v
script (Stage 5)
|
v
revision (Stage 6)
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.
- yesterday Changed 00f7ea27165b
- 2mo ago First seen · 171 lines · 66 tokens per session scan A c3966e58849e
talk-pipeline is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (43 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,537 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
app-store-screenshots
Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS and/or Android apps, or creating programmatic screenshot generators with Next.js. Triggers on app store, play store, screenshots, marketing assets, html-to-image, phone mockup, android screenshots, feature…
content
Content production and SEO writing skills. Blog posts, long-form content research, structured content frameworks, audience-targeted writing, content optimization. Triggers on: blog, content writing, article, copywriting, content strategy, content brief, SEO content, audience research.
expo-app-config
Choosing between app.json vs app.config.ts vs app.config.js, environment variables, variants, extra fields, plugin chain, and slug/scheme/bundle/version discipline. Triggers on app.json, app.config.ts, app.config.js, expo config, environment variable, .env, eas secret, variant, extra field, slug, scheme, bundle…
expo-modules
Writing Swift/Kotlin native modules with the Expo Modules API, requireNativeModule, async functions, view modules, and the event-emitter pattern. Triggers on expo modules, native module, swift, kotlin, requireNativeModule, expo-module-scripts, expo.modules.json, view module, event emitter, native function, async…
expo-notifications
Push and local notification setup with expo-notifications. iOS (APNs) + Android (FCM) credentials, permission flow, channels (Android 8+), categories, and scheduled notifications.
expo-config-plugin
Writing Expo config plugins, withInfoPlist, withAndroidManifest, withDangerousMod, mod compose, plugin testing, and registration in app.config.ts. Triggers on config plugin, with-plugin, withInfoPlist, withAndroidManifest, withDangerousMod, withEntitlementsPlist, withGradleProperties, mod, native config, expo plugin…