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 skills/hoavdc/codexkit/codexkit-onboarding-plan-creatornpx skills add hoavdc/CodexKit --skill codexkit-onboarding-plan-creatorgit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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.00070 | $0.01290 |
| Opus 5 | $0.00035 | $0.00645 |
| Sonnet 5 | $0.00014 | $0.00258 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
codexkit-onboarding-plan-creator 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 2d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Plan Creator
When to Use
- When a new hire is confirmed and start date is set
- When HR or a hiring manager needs a structured onboarding checklist
- When revamping the onboarding process for a team or department
- When onboarding remote or hybrid employees
Procedure
Step 1 — Pre-Boarding (Before Day 1)
- Send welcome email with start date, dress code, parking, and first-day agenda
- Set up accounts: email, Slack, HRIS, project tools, VPN
- Assign buddy/mentor from the team
- Prepare workstation (physical or virtual)
- Share pre-reading: company handbook, team wiki, org chart
Step 2 — Day 1
- Welcome meeting with manager (30 min)
- HR orientation: policies, benefits enrollment, emergency contacts
- IT setup verification
- Buddy introduction and office/virtual tour
- First lunch with team
Step 3 — Week 1
- Role overview and expectations alignment with manager
- Meet key stakeholders (1:1 coffee chats)
- Review current projects and team roadmap
- Complete compliance training (security, harassment, data privacy)
- End-of-week check-in with manager
Step 4 — 30-Day Milestone
- Complete all mandatory training
- Understand team processes and tools
- Take ownership of first small task or project
- Feedback session with manager: "What's going well? What's confusing?"
- Buddy check-in
Step 5 — 60-Day Milestone
- Contribute independently to team deliverables
- Build relationships across departments
- Identify one process improvement suggestion
- Manager feedback: progress vs expectations
- Probation mid-point review (if applicable)
Step 6 — 90-Day Milestone
- Fully integrated into team workflows
- Set first performance goals (aligned with team OKRs)
- Present a "What I've learned" summary to team (optional)
- Manager evaluation: confirm role fit and probation pass
- Transition from onboarding to regular 1:1 cadence
Inputs
| Input | Required | Format |
|---|---|---|
| Role / job title | Yes | Text |
| Department | Yes | Text |
| Start date | Yes | Date |
| Reporting manager | Yes | Name |
| Tools/systems used | Recommended | List |
| Buddy assignment | Recommended | Name |
What ships with it
4 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.
- 2d ago First seen · 158 lines · 70 tokens per session scan A 9f972cc78fe9
codexkit-onboarding-plan-creator is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 1,290 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-08-30.
Other skills, from other repositories
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.