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 agentmods add skills/cwinvestments/memstack/webinar-scriptnpx skills add cwinvestments/memstack --skill webinar-scriptgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/cwinvestments/memstack/webinar-script)<a href="https://agentmods.dev/skills/cwinvestments/memstack/webinar-script"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/webinar-script.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.03176 |
| Opus 5 | $0.00032 | $0.01588 |
| Sonnet 5 | $0.00013 | $0.00635 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
memstack-marketing-webinar-script 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webinar Script: Writing presentation script...
Produces a full timestamped webinar script with hook, teaching segments, offer transition, Q&A handling, CTA placement, slide suggestions, and replay follow-up email sequence.
Activation
When this skill activates, output:
Webinar Script: Writing presentation script...
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User says "webinar script", "webinar", "live presentation" | ACTIVE |
| User says "teach-to-sell" or "presentation script" | ACTIVE |
| User wants a scripted webinar with CTA and offer | ACTIVE |
| User wants a static sales page | DORMANT: use Landing Page Copy |
| User wants a launch timeline | DORMANT: use Launch Plan |
Common Mistakes
| Mistake | Why It's Wrong |
|---|---|
| "Teach everything you know" | Overwhelmed attendees don't buy. Teach ONE framework, leave them wanting more. |
| "Pitch at the beginning" | Teach first (30+ minutes), then transition to the offer. Trust before transaction. |
| "Skip the origin story" | People buy from people they relate to. Your story builds connection and credibility. |
| "Ignore the chat" | Engagement in the first 10 minutes predicts attendance through the offer. Prompt interaction early. |
| "No urgency on the offer" | Webinar-only bonuses and deadlines create 60%+ of webinar revenue. |
Protocol
Step 1: Gather Webinar Requirements
If the user hasn't provided details, ask:
- Topic: what will you teach? (one specific transformation)
- Offer: what are you selling? (name, price, format)
- Audience: who is attending? (experience level, pain points)
- Duration: how long? (60 min standard, 90 min for high-ticket)
- Format: live or evergreen (pre-recorded)?
- Platform: Zoom, WebinarJam, Demio, YouTube Live?
Step 2: Structure the Webinar
Standard 60-minute webinar structure:
| Segment | Time | Duration | Purpose |
|---|---|---|---|
| Opening hook | 0:00 | 3 min | Grab attention, state the promise |
| Introduction & credibility | 3:00 | 5 min | Build trust, share origin story |
| Content pillar 1 | 8:00 | 12 min | Teach framework step 1 |
| Content pillar 2 | 20:00 | 12 min | Teach framework step 2 |
| Content pillar 3 | 32:00 | 10 min | Teach framework step 3 |
| Transition to offer | 42:00 | 3 min | Bridge teaching to selling |
| The offer | 45:00 | 10 min | Present the product with value stack |
| Q&A | 55:00 | 5+ min | Handle objections, close sales |
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 7771b833e703
- yesterday First seen · 398 lines · 65 tokens per session scan A 8890efc183d2
memstack-marketing-webinar-script is a skill published in the GitHub repository cwinvestments/memstack (419 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 3,176 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
context7-docs
Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…