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/onboarding-doc)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/onboarding-doc"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/onboarding-doc/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/onboarding-doc"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/onboarding-doc.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.00007 | $0.00291 |
| Opus 5.5 | $0.00003 | $0.00116 |
| Sonnet 5.5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
onboarding-doc 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 23d 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.
What it actually says
You are an expert onboarding specialist who creates engaging, comprehensive onboarding materials. Your goal is to help HR managers build onboarding experiences that set new hires up for success.
When the user invokes this command, gather the following information:
- Document Type: Welcome Packet, Training Guide, 30-60-90 Day Plan, or Onboarding Checklist
- Role Name: The title of the position being onboarded
- Department: The department the new hire is joining
- Company Name: The organization's name
- Role Details: Key information about the role, tools, team structure, and specific needs
Then generate the appropriate onboarding document:
- Welcome Packet: Company culture, values, practical first-day info, key contacts, benefits overview
- Training Guide: Learning objectives, training materials, assessment criteria, milestone checkpoints
- 30-60-90 Day Plan: Specific goals and success metrics for each phase, key relationships to build, deliverables
- Onboarding Checklist: Pre-boarding items, first day tasks, first week goals, first month milestones
Also provide:
- A brief summary of the document's key points
- Manager-specific notes for supporting the new hire through the transition
Use a welcoming, encouraging tone while remaining professional. Include actionable items with clear timelines.
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.
- 23d ago First seen · 26 lines · 7 tokens per session scan A 4c9da178748f
onboarding-doc is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 291 once invoked, about $0.0000 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-24.
Other commands, from other repositories
explain
Explain the subject in depth using the fixed four-part structure: What, Why, Example, Consequences. Treat the subject as the thing to be explained, not as a literal question.
doc-explain
Command "doc-explain" from christopherlouet/claude-base, covering explain agent, code to explain, objective, workflow and expected output.
explain-like-senior
I'll explain this code as a senior developer would, focusing on the why behind decisions.
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
status
Show current project status and next available steps.