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 pawbytes/skill-suites --skill paw-wbc-setupgit clone --depth 1 https://github.com/pawbytes/skill-suitesWrote 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/pawbytes/skill-suites/paw-wbc-setup)<a href="https://agentmods.dev/skills/pawbytes/skill-suites/paw-wbc-setup"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-wbc-setup/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/pawbytes/skill-suites/paw-wbc-setup"><img src="https://agentmods.dev/badge/skills/pawbytes/skill-suites/paw-wbc-setup.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.00039 | $0.01234 |
| Opus 5.5 | $0.00016 | $0.00494 |
| Sonnet 5.5 | $0.00008 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
paw-wbc-setup 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webinar Creator Suite Setup
Overview
Installs and configures the Webinar Creator Suite module into a project. This module is a guided pipeline that takes solo creators from a vague webinar idea to a production-ready slide deck outline and script.
Creates the output directory structure and orientation files:
{project-root}/.pawbytes/webinar-suites/— module root{project-root}/.pawbytes/webinar-suites/index.md— orientation file tracking webinars and status{project-root}/.pawbytes/webinar-suites/webinars/— webinar workspaces{project-root}/.pawbytes/webinar-suites/daily/— daily activity logs
{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root.
Principles
- Idempotent setup: Running setup multiple times should not destroy existing work
- Minimal configuration: Only collect essential config; inherit from core Pawbytes settings where possible
- Clear confirmation: Always show what was created before completing
- Respect existing config: Never overwrite user preferences without explicit consent
On Activation
- Read
./assets/module.yamlfor module metadata - Check if
{project-root}/.pawbytes/webinar-suites/exists — if present, inform the user this is an update - Check for core Pawbytes config at
{project-root}/.pawbytes/config/config.yaml
If the user provides arguments (e.g. accept all defaults, --headless), skip interactive prompting and use defaults.
Inline value mapping: Users can also provide specific values inline using natural language (following Pawbytes convention). Parse key-value pairs from the invocation and apply them directly:
- "my name is Alice" →
user_name: Alice - "use Indonesian" →
communication_language: Indonesian - "user name is Alice, language is Indonesian" → Apply both values
This allows non-interactive setup with custom values without requiring full flag syntax.
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.
- 1mo ago First seen · 129 lines · 39 tokens per session scan A 9c865a3b2297
paw-wbc-setup is a skill published in the GitHub repository pawbytes/skill-suites (114 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 1,234 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…