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 indranilbanerjee/digital-marketing-pro --skill webinar-plangit clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-proWrote 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/indranilbanerjee/digital-marketing-pro/webinar-plan)<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/webinar-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/webinar-plan/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/indranilbanerjee/digital-marketing-pro/webinar-plan"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/webinar-plan.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.00030 | $0.01487 |
| Opus 5.5 | $0.00012 | $0.00595 |
| Sonnet 5.5 | $0.00006 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
webinar-plan 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:webinar-plan
Purpose
Plan a webinar or virtual event from concept to post-event follow-up, including content structure, promotion strategy, registration optimization, engagement tactics, and measurement framework. Produces a complete execution package that a team can implement without further strategic planning.
Input Required
The user must provide (or will be prompted for):
- Topic/theme: Subject matter and angle for the webinar — what specific problem or opportunity will be addressed
- Target audience: Who should attend — role, seniority, industry, company size, experience level, and pain points
- Objectives: Primary goal — lead generation, education, product demo, thought leadership, customer retention, or partner enablement
- Preferred platform: Webinar tool in use or under consideration (Zoom, Teams, Webex, GoToWebinar, Livestorm, StreamYard, etc.)
- Date/time: Proposed date and time with timezone (or ask for optimal scheduling recommendation based on audience)
- Speakers: Presenters, panelists, or hosts — internal team members and/or external guests with their expertise areas
- Budget for promotion: Available spend for driving registrations — paid ads, sponsorships, influencer partnerships, etc.
- Expected attendance: Target registration and attendance numbers for goal-setting and promotion planning
- Content assets available: Existing slide decks, research reports, demos, or content that can be repurposed for the webinar
- Follow-up goals: What should happen after the webinar — sales meetings booked, free trial signups, content downloads, community joins
Process
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at~/.claude-marketing/brands/{slug}/guidelines/_manifest.json— if present, load restrictions and relevant category files. Check for custom templates at~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. - Define webinar format: Select the best format based on objectives, audience preferences, and speaker strengths — presentation, panel discussion, interactive workshop, product demo, AMA, fireside chat, or hybrid format with multiple segments
- Create content outline with timing: Build a minute-by-minute run of show — opening hook, speaker introductions, content segments with transitions, audience interaction points (polls, Q&A breaks), and closing CTA with time allocations for each block
- Design registration page copy: Write headline, subheadline, 3-5 key takeaway bullets, speaker bios with credibility markers, urgency elements (limited spots, countdown), and social proof (past attendee quotes, company logos) optimized for conversion
- Build multi-channel promotion plan: Create a coordinated promotion strategy across email sequences, organic social posts, paid ads (LinkedIn, Meta, Google), partner/speaker cross-promotion, blog/website banners, community outreach, and internal employee advocacy
- Create presenter prep materials: Develop speaker brief with key talking points, slide structure recommendations, audience profile context, brand voice reminders, Q&A preparation, and technical setup/rehearsal checklist
- Design attendee engagement strategy: Plan interactive elements — specific poll questions tied to content, Q&A facilitation approach, chat prompts to spark discussion, breakout room activities (if applicable), live resource sharing, and real-time feedback mechanisms
- Plan post-event sequence: Design the complete follow-up funnel — recording availability timeline, segmented email sequences for attendees vs. no-shows, lead scoring criteria based on engagement, sales handoff process for high-intent leads, and content repurposing plan (blog post, social clips, podcast episode, infographic)
- Define success metrics: Set targets for registrations, show-up rate, engagement rate (poll participation, questions asked, chat activity), leads generated, pipeline influenced, and attendee satisfaction — with industry benchmark comparisons
- Create day-of checklist: Build a comprehensive run-of-day timeline covering tech setup and testing, dry run schedule, backup plans for speaker or tech failures, moderator duties minute-by-minute, recording confirmation, and immediate post-event actions
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.
- 4d ago Changed · -115 tokens per session b4254835341b
- 9d ago First seen · 64 lines · 145 tokens per session scan A 03967c4ff15b
webinar-plan is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (882 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,487 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-10-05.
Other skills, from other repositories
cf-brief
Write a research-backed content brief from a keyword or topic: intent, competitors, outline. "brief me on this topic".
cf-publish
Publish a reviewed piece to Webflow or WordPress as draft, scheduled or live. "push this live to WordPress".
cf-template
Create a custom content-type template: sections, word counts, citation minimums. "make a template for our case studies".
cf-variants
Generate scored A/B variants of a headline, opening line, hook or CTA, with a test plan. "give me headline options to test".
cf-translate
Translate a finished piece into 15 languages, keeping brand voice and citations; literal, adapted or transcreated. "translate this into Spanish".
cf-video-script
Write a timestamped video script with B-roll and on-screen text for YouTube, Shorts or Reels. "turn this into a video script".