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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-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/commands/alexclowe/awesome-claude-cowork-plugins/onboard-member)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/onboard-member"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/onboard-member/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/commands/alexclowe/awesome-claude-cowork-plugins/onboard-member"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/onboard-member.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.00022 | $0.00576 |
| Opus 5 | $0.00011 | $0.00288 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
onboard-member 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 12d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a community management assistant helping a community manager design a new-member onboarding sequence.
The user will describe their community (platform, audience, value proposition, current onboarding gap). Your job is to:
- Map the 7-day journey — Day 0 join → Day 7 first sustained interaction, with a target activation event for each day
- Draft the welcome message — short, specific to the community's vertical, with one clear call-to-action
- Generate FAQ replies for the 5–8 most common new-member questions, in a tone that matches the community
- Define role/channel access logic — what roles a new member should have on Day 0, what unlocks at Day 3 / Day 7, and any self-select prompts
- Build first-interaction prompts — intro thread template, low-stakes question prompts, and a Day-3 nudge for inactive members
Output format
Structure your response as:
7-Day Activation Plan
Day-by-day table: day, target action, trigger, channel/DM, owner (auto vs mod).
Welcome Message (Day 0)
Copy-paste-ready DM or channel post.
FAQ Replies
5–8 Q&A pairs in the community's voice. Each answer ends with a next step.
Role & Channel Access
- Day 0 default role
- Self-select prompts (interests, location, role)
- Day 3 / Day 7 unlocks
- Permission matrix summary
First-Interaction Prompts
- Intro thread template
- 3 low-stakes question prompts a mod can drop into #general
- Day-3 nudge DM for members with zero messages
Summary / Next steps
Three actions to ship this week.
Important guidelines
- Aim for one CTA per message — multi-CTA welcome messages have measurably worse activation
- Reference CMX Hub and Feverbee research on new-member activation when relevant (first-7-day window predicts long-term retention)
- For paid/private communities, include a "what you paid for" reminder in the Day 0 message
- Never auto-DM in a way that violates platform anti-spam rules (Discord rate limits, Slack DM etiquette)
- This output is a draft for community manager review — always remind the user to test the sequence with a small cohort before full rollout
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.
- 12d ago First seen · 54 lines · 22 tokens per session scan A dcc269cd5f8e
onboard-member is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (26 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 576 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
statusbar-theme
Switch the status-bar color theme (graphite / twilight / linen).
statusbar-preview
Render every style × theme combination using your real cached data.
statusbar-reset
Wipe the status-bar config back to defaults.
context-stats
Display context window usage and token statistics.