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 w95/awesome-claude-corporate-skills --skill onboarding-plannergit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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/w95/awesome-claude-corporate-skills/onboarding-planner)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/onboarding-planner"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/onboarding-planner/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/w95/awesome-claude-corporate-skills/onboarding-planner"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/onboarding-planner.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.00068 | $0.04477 |
| Opus 5 | $0.00034 | $0.02239 |
| Sonnet 5 | $0.00014 | $0.00895 |
| Haiku 4.5 | $0.00007 | $0.00448 |
Grade A, and why
onboarding-planner 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 9d 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Planner
Overview
This skill helps create structured, engaging onboarding experiences that help new hires succeed quickly while building connection to company culture and team. It provides frameworks for 30-60-90 day plans, first-week activities, training schedules, buddy programs, welcome packages, and success metrics that drive productivity, retention, and engagement.
When to Use This Skill
- Planning onboarding for a new hire
- Creating role-specific onboarding playbooks
- Designing first-week and first-month activities
- Building 30-60-90 day milestone plans
- Establishing buddy or mentor programs
- Creating onboarding checklists and templates
- Improving onboarding consistency across team
- Designing welcome packages and experiences
- Building training and knowledge transfer plans
- Creating measurement frameworks for onboarding success
Key Components
1. Pre-Arrival Phase (Before Day 1)
Two Weeks Before Arrival:
- Send welcome email with company info, photos of workspace/team
- Share org chart, company handbook, culture overview
- Provide logistics: address, parking, arrival time, who to ask for
- Arrange any equipment needs (laptop, monitor, supplies)
- Arrange pre-arrival video calls with manager and key teammates
- Send cultural context: company values, recent wins, key projects
One Week Before Arrival:
- Prepare workspace: desk setup, welcome gift, supplies
- Brief team on new hire's background and role
- Assign buddy (peer mentor for culture/logistics)
- Schedule first-day meetings with stakeholders
- Prepare onboarding materials (handbook, org info, training schedule)
- Setup system access: email, Slack, tools, building access
- Create first-week calendar with meetings and activities
- Prepare welcome package or surprise (team lunch plans, etc.)
Day Before Arrival:
- Confirm arrival time and logistics with new hire
- Remind team member meeting schedule
- Do final workspace check
- Prepare manager's onboarding checklist
- Review new hire's background notes
- Prepare informal Q&A materials
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.
- 9d ago First seen · 556 lines · 68 tokens per session scan A df5432e0dd2c
onboarding-planner is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 68 tokens to every session and 4,477 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
workflow
Starts and manages autonomous agent workflows. Triggers: workflow, start workflow, autonomous agents, agent pipeline.
autonomous-dev
Drives a brief, specification, issue or existing PR through implementation, review, tests and QA to a ready PR. Persists ownership, progress and commit-bound evidence for safe resumption. Use for autonomous software delivery or finishing an interrupted development run.
onboard
Sets up ai-toolkit in a project: symlinks, CLAUDE.md, intent interview. Triggers: onboard, setup project, install ai-toolkit, migrate project.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
prd-to-issues
Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.
prd-to-plan
Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.