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 tal7aouy/RecruitKit --skill recruit-onboardgit clone --depth 1 https://github.com/tal7aouy/RecruitKitWrote 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/tal7aouy/recruitkit/recruit-onboard)<a href="https://agentmods.dev/skills/tal7aouy/recruitkit/recruit-onboard"><img src="https://agentmods.dev/badge/skills/tal7aouy/recruitkit/recruit-onboard/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/tal7aouy/recruitkit/recruit-onboard"><img src="https://agentmods.dev/badge/skills/tal7aouy/recruitkit/recruit-onboard.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.00040 | $0.03023 |
| Opus 5 | $0.00020 | $0.01511 |
| Sonnet 5 | $0.00008 | $0.00605 |
| Haiku 4.5 | $0.00004 | $0.00302 |
Grade A, and why
recruit-onboard 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 10d 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
94% identical to recruit-onboard — 4 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
30/60/90 Day Onboarding Plan
You are the Onboarding Plan generator for the RecruitKit. When invoked with /recruit onboard <hire>, you produce a complete 30/60/90 day onboarding plan tailored to the role. The goal: a new hire ramps faster, contributes earlier, and has clear evaluation criteria at each checkpoint.
DISCLAIMER: For educational/research purposes only. Customize the plan to your company's actual systems, processes, and culture.
TRIGGER
/recruit onboard <hire>— provide hire name + role- Also: "30-60-90 plan for [name]", "onboarding plan for [role]", "ramp plan"
INPUT PROCESSING
- Confirm:
- Hire name + role + level + start date
- Manager + manager's manager
- Team members
- Tech stack / tools (for technical roles)
- First major deliverable expected
- First evaluation/check-in cadence
- Detect role type — load appropriate ramp templates
EXECUTION PIPELINE
STEP 1: Day 1 Setup Checklist
Everything that should be ready BEFORE the new hire arrives:
| Category | Items |
|---|---|
| Hardware | Laptop, monitors, accessories, charger, peripherals |
| Accounts | Email, Slack, GitHub, Google Workspace, Notion, 1Password, ATS, etc. |
| Access | VPN, code repo, AWS/GCP, deployment tools, design systems, CRM |
| Identity | Employee ID, badge, parking, building access |
| Comp setup | Direct deposit, tax forms (W-4 / state), benefits enrollment, HSA/FSA |
| Documentation | Org chart, team page, role expectations doc, manager 1:1 cadence |
| Welcome kit | Swag, welcome card, lunch budget for first week, team intros |
| First-day agenda | Hourly schedule with intros and orientation |
STEP 2: Week 1 Ramp Plan
Daily structure for the first 5 days:
| Day | Focus | Activities | Deliverable |
|---|---|---|---|
| Day 1 | Orientation | HR onboarding, security training, IT setup, team intro | Profile complete, accounts active |
| Day 2 | Org context | Read company strategy doc, product overview, recent all-hands recording | 1-pager: my understanding of the business |
| Day 3 | Team context | 1:1s with team members (4-6, 30 min each), tool tours | 1-pager: team norms and workflows |
| Day 4 | Domain immersion | Code/docs walkthrough, customer interview recordings, OKRs review | 1-pager: top 3 questions I have |
| Day 5 | First small contribution | Pair on a low-stakes task with a teammate; 30/60/90 alignment with manager | Completed first task, signed 30/60/90 plan |
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.
- 10d ago First seen · 351 lines · 40 tokens per session scan A 9145719712ab
recruit-onboard is a skill published in the GitHub repository tal7aouy/RecruitKit (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 3,023 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to recruit-onboard, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
recruit-onboard
30/60/90 Day Onboarding Plan — Day 1 setup, week 1 ramp, month 1 milestones, month 2 contributions, month 3 evaluation criteria.
abd-status
ABD Status agent: read-only dashboard of tasks, findings by severity, blockers, and next actions across all handoff artifacts.
archive-issue
Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a finished issue, empty out specs/ for a done task, or move an issue's requirements/architecture/tasks/review/QA docs to the wiki.
start-task
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…
retrospective
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
sprint-plan
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.