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 The-AI-Directory-Company/agents-and-skills --skill onboarding-plangit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/onboarding-plan)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/onboarding-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/onboarding-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/the-ai-directory-company/agents-and-skills/onboarding-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/onboarding-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.00032 | $0.01649 |
| Opus 5 | $0.00016 | $0.00825 |
| Sonnet 5 | $0.00006 | $0.00330 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
onboarding-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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Plan
Before you start
Gather the following from the user:
- Who is being onboarded? (New hire, new customer, or new user — and their role/persona)
- What does "fully ramped" look like? (3-5 concrete outcomes that indicate onboarding is complete)
- What is the expected ramp timeline? (30 days, 60 days, 90 days)
- Who is responsible for the onboarding? (Manager, buddy, CSM, or self-guided)
- What existing resources are available? (Documentation, training videos, sandbox environments, mentors)
If the user says "we just need a checklist," push back: "A checklist gets tasks done but doesn't ensure understanding. What should this person be able to do independently by the end of onboarding?"
Onboarding plan template
1. Onboarding Overview
Define the onboarding scope in a brief summary.
Onboardee type: New hire — Senior Frontend Engineer
Team: Consumer Products
Timeline: 90 days (30-60-90 structure)
Onboarding owner: Engineering Manager + assigned buddy
Success measure: Ships first production feature independently by Day 75
2. Pre-Start Preparation
Complete before the onboardee's first day:
- Access provisioning: List every system, tool, and repo they need access to. Include account names and who provisions each one.
- Equipment setup: Laptop, monitors, peripherals — ordered and configured.
- Welcome packet: Team org chart, key contacts, calendar invites for recurring meetings, links to onboarding docs.
- Buddy assignment: Assign a peer (not the manager) who is available for daily questions during the first two weeks.
- First-week calendar: Pre-schedule all Day 1-5 meetings and activities. An empty calendar on Day 1 signals disorganization.
3. Milestone-Based Progression
Structure the plan into milestones, not a flat task list. Each milestone has a clear success criterion.
Milestone 1: Orientation (Days 1-7)
| Day | Activity | Owner | Success Criterion |
|---|---|---|---|
| 1 | Welcome meeting with manager — role expectations, 90-day goals | Manager | Goals documented and shared |
| 1 | Dev environment setup with buddy | Buddy | Can build and run the app locally |
| 2 | Architecture walkthrough — system overview, key services | Tech lead | Can draw the high-level architecture from memory |
| 3 | Codebase tour — repo structure, CI/CD pipeline, deployment process | Buddy | Successfully deploys a test change to staging |
| 4-5 | Read team docs — ADRs, runbooks, on-call playbook | Self | Completes reading, notes questions for buddy |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 122 lines · 32 tokens per session scan A 1e946f3141fa
onboarding-plan is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 1,649 once invoked, about $0.0002 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
career-path-planner
Career goal mapping with skill gap analysis, actionable development plans, and milestone tracking. Use when planning career transitions, identifying skill gaps, setting professional development goals, or evaluating career options.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
course-material-creator
Create custom educational materials including syllabi, lesson plans, assessments, reading lists, and learning objectives. Use when building course curricula, training programs, workshops, or educational content.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.