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 SkillMedev/course-creator-launch-system --skill community-engagement-playbookgit clone --depth 1 https://github.com/SkillMedev/course-creator-launch-systemWrote 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/skillmedev/course-creator-launch-system/community-engagement-playbook)<a href="https://agentmods.dev/skills/skillmedev/course-creator-launch-system/community-engagement-playbook"><img src="https://agentmods.dev/badge/skills/skillmedev/course-creator-launch-system/community-engagement-playbook/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/skillmedev/course-creator-launch-system/community-engagement-playbook"><img src="https://agentmods.dev/badge/skills/skillmedev/course-creator-launch-system/community-engagement-playbook.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.00125 | $0.01984 |
| Opus 5 | $0.00063 | $0.00992 |
| Sonnet 5 | $0.00025 | $0.00397 |
| Haiku 4.5 | $0.00013 | $0.00198 |
Grade A, and why
community-engagement-playbook 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 11d 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.
This is a copy
100% identical to community-engagement-playbook — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Engagement Playbook
A course community exists for exactly two outputs: completion and testimonials. Students who feel seen finish, finished students get results, and results become the proof that sells the next cohort. The costly mistake is treating community as a feature to bolt on - an empty Slack nobody posts in signals a dead course louder than no community at all, and an unbudgeted community quietly consumes the creator's production time until the next launch slips.
This skill runs after launch-email-sequence hands over the buyers, operates against the completion target set by course-outline-architect, and feeds its testimonial harvest back to course-sales-page's proof section. That loop - community to testimonials to sales page - is what makes the second launch outperform the first.
Worked example throughout: Dana, who just closed the "Notion OS for Consultants" launch ($297) with roughly 120 students from her 8,000-subscriber list, budgeting 5 hours a week for community.
Operating procedure
Step 1: Collect the inputs
- Student count and where the audience already hangs out (check where they replied from during the launch; ask 5 buyers directly if unknown).
- The course's quick-win moment and module milestones from course-outline-architect.
- The creator's honest weekly hours available. Default and hard cap: 5.
- Course length and the completion target - this pack designs for 35 percent or better against the 10 to 15 percent industry average.
Step 2: Choose the platform - where students already are beats features
Rank candidates by one question: which platform are these students already opening daily? A feature-rich community platform they must remember to visit loses to a mediocre one already in their dock. Decision rules:
- Students live in Slack for work (Dana's consultants do): Slack or a Slack-adjacent tool wins, features be damned.
- Audience is creators/gamers already on Discord: Discord.
- Buying a dedicated tool (Circle, Skool, and kin) is right only when the cohort is large enough to sustain its own gravity - under roughly 50 active students, a dedicated platform usually reads as empty.
- Never more than one platform. Splitting 120 students across two places produces two ghost towns.
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.
- 11d ago First seen · 116 lines · 125 tokens per session scan A 416be0b0ae05
community-engagement-playbook is a skill published in the GitHub repository SkillMedev/course-creator-launch-system (1 stars, last pushed 2mo ago), licensed MIT. It adds 125 tokens to every session and 1,984 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to community-engagement-playbook, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
creative-commons-explainer
Explains a specific Creative Commons licence in plain language, telling a media professional exactly what they can and cannot do with the licensed content — including attribution requirements, commercial use rules, and derivative work restrictions.
understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase.
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
master-atisha
A reference-based assistant for Atisha and the Kadam school, an early Tibetan Buddhist tradition. It explains the staged path to awakening and can answer in Atisha’s historical teaching style.