Borrowing it
Nothing to install: this file belongs to dtsola/xiaoyaopeipei. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dtsola/xiaoyaopeipei/main/.claude/commands/onboard.mdgit clone --depth 1 https://github.com/dtsola/xiaoyaopeipeiWrote 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/dtsola/xiaoyaopeipei/onboard)<a href="https://agentmods.dev/commands/dtsola/xiaoyaopeipei/onboard"><img src="https://agentmods.dev/badge/commands/dtsola/xiaoyaopeipei/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.1 | $0.00000 | $0.00814 |
| Opus 5 | $0.00000 | $0.00407 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
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 6d 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
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Command: Onboard
This command acts as an expert technical mentor to help you rapidly understand a new codebase, generating a comprehensive "Survival Guide" for the project.
Usage
To analyze the project, run:
/onboard
Or with specific focus:
/onboard --focus "auth flow"
What This Command Does
- Scans Context: Automatically reads key configuration files to determine the tech stack:
package.json/go.mod/pom.xml/requirements.txt(Dependencies)README.md(Documentation)docker-compose.yml/Dockerfile(Infrastructure).gitignore(Project structure hints)
- Maps Architecture: Analyzes the directory structure (
src,app,lib, etc.) to understand the architectural pattern (MVC, DDD, Hexagonal, etc.). - Traces Core Paths: Identifies the entry points (e.g.,
index.js,main.go,App.tsx) and traces a theoretical request from API to Database. - Synthesizes Report: Generates a structured Markdown report covering Business, Architecture, Code Navigation, and Setup.
Output Structure: The Survival Guide
The command will generate a report with the following structure:
1. 🔭 The Big Picture (Business & Architecture)
- One-Liner: What does this project actually do?
- Tech Stack: Core languages, frameworks, and why they seem to be used.
- Architecture Diagram: A
mermaidflowchart showing the high-level system design or data flow.
2. 🗺️ Map of the Territory (Navigation)
- Key Directories: The top 3-5 most important folders and what lives inside.
- Logic Location: Where does the business logic live? (Controllers? Services? Domain?)
- Entry Points: Where does the code start running?
3. 🕵️ Core Path Analysis
- Trace: A step-by-step list tracking a core feature (e.g., Login or Create Order) from the HTTP Request down to the Database Query.
- Data Flow:
Function A->Function B->Database Table.
4. 🚀 Setup & Run
- Quick Start: Summarized commands to get it running (based on
package.jsonscripts or Docker). - Pitfalls: 2 predicted issues a new developer might face (e.g., missing ENV variables, version mismatches).
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.
- 6d ago First seen · 71 lines · 0 tokens per session scan A 66196628a038
onboard is a command published in the GitHub repository dtsola/xiaoyaopeipei (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 814 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
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
create-page
Create a new Next.js page with appropriate rendering strategy and boilerplate.
coverage-report
Generate and display test coverage report with analysis and recommendations.
estimate-azure-cost
Estimate Azure resource costs and provide optimization recommendations.
estimate-gcp-cost
Estimate GCP resource costs and provide optimization recommendations.
auth
Авторизация Telegram-сессии через MCP-tools (без терминала).