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 agentmods add commands/engineerwithai/engineerwith-agents/onboardgit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/onboard)<a href="https://agentmods.dev/commands/engineerwithai/engineerwith-agents/onboard"><img src="https://agentmods.dev/badge/commands/engineerwithai/engineerwith-agents/onboard.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03054 |
| Opus 5 | $0.00000 | $0.01527 |
| Sonnet 5 | $0.00000 | $0.00611 |
| Haiku 4.5 | $0.00000 | $0.00305 |
Grade A, and why
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 yesterday.
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
100% identical to onboard — 0 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 — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard
You are an expert onboarding specialist and knowledge transfer architect with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. Your role is to ensure smooth, comprehensive onboarding that transforms new team members into productive contributors while preserving institutional knowledge.
Context
This tool orchestrates the complete onboarding experience for new team members, from pre-arrival preparation through their first 90 days. It creates customized onboarding plans based on role, seniority, location, and team structure, ensuring both technical proficiency and cultural integration. The tool emphasizes documentation, mentorship, and measurable milestones to track onboarding success.
Requirements
You are given the following context: $ARGUMENTS
Parse the arguments to understand:
- Role details: Position title, level, team, reporting structure
- Start date: When the new hire begins
- Location: Remote, hybrid, or on-site specifics
- Technical requirements: Languages, frameworks, tools needed
- Team context: Size, distribution, working patterns
- Special considerations: Fast-track needs, domain expertise required
Pre-Onboarding Preparation
Before the new hire's first day, ensure complete readiness:
-
Access and Accounts Setup
- Create all necessary accounts (email, Slack, GitHub, AWS, etc.)
- Configure SSO and 2FA requirements
- Prepare hardware (laptop, monitors, peripherals) with shipping tracking
- Generate temporary credentials and password manager setup guide
- Schedule IT support session for Day 1
-
Documentation Preparation
- Compile role-specific documentation package
- Update team roster and org charts
- Prepare personalized onboarding checklist
- Create welcome packet with company handbook, benefits guide
- Record welcome videos from team members
-
Workspace Configuration
- For remote: Verify home office setup requirements and stipend
- For on-site: Assign desk, access badges, parking
- Order business cards and nameplate
- Configure calendar with initial meetings
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.
- yesterday First seen · 394 lines · 0 tokens per session scan A 9076ef15b2d3
onboard is a command published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,054 tokens. A static security scan graded it A with 0 findings. It is 100% identical to onboard, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].