xiaoyaoprivatebill: Command for Claude Code

.claude/commands/onboard.md

onboard is a command for Claude Code from dtsola/xiaoyaoprivatebill. It costs 0 tokens per session (814 once invoked), scanned A, original, MIT.

A command that studies an unfamiliar codebase and creates a Markdown survival guide for it. It reads project configuration, maps the folder structure, and describes how important code paths work.

In plain words
What is it for?
Understanding a project’s technology stack, finding its main entry points, tracing a request from an API to a database, and documenting setup, architecture, and code navigation.
Why use it?
Starting in a new repository often means spending time discovering its tools, architecture, setup, and entry points. The report gathers that orientation information in one document.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is dtsola/xiaoyaoprivatebill's own configuration. It tells Claude Code how to work on xiaoyaoprivatebill itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything xiaoyaoprivatebill configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dtsola/xiaoyaoprivatebill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dtsola/xiaoyaoprivatebill/main/.claude/commands/onboard.md
Clone the repo
git clone --depth 1 https://github.com/dtsola/xiaoyaoprivatebill

Made for: Claude Code.

Wrote 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.

agentmods badge for onboard

README.md
[![agentmods](https://agentmods.dev/badge/commands/dtsola/xiaoyaoprivatebill/onboard/github.svg)](https://agentmods.dev/commands/dtsola/xiaoyaoprivatebill/onboard)
Your own site
<a href="https://agentmods.dev/commands/dtsola/xiaoyaoprivatebill/onboard"><img src="https://agentmods.dev/badge/commands/dtsola/xiaoyaoprivatebill/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.

agentmods 80×15 button for onboard

Your own site · 80×15
<a href="https://agentmods.dev/commands/dtsola/xiaoyaoprivatebill/onboard"><img src="https://agentmods.dev/badge/commands/dtsola/xiaoyaoprivatebill/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 66196628a038, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • onboard — 100% identical, 0 lines differ
.claude/commands/onboard.md · 71 lines

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

  1. 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)
  2. Maps Architecture: Analyzes the directory structure (src, app, lib, etc.) to understand the architectural pattern (MVC, DDD, Hexagonal, etc.).
  3. Traces Core Paths: Identifies the entry points (e.g., index.js, main.go, App.tsx) and traces a theoretical request from API to Database.
  4. 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 mermaid flowchart 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.json scripts or Docker).
  • Pitfalls: 2 predicted issues a new developer might face (e.g., missing ENV variables, version mismatches).

Read the full file on GitHub · 71 lines

Changes

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.

  1. 9d ago First seen · 71 lines · 0 tokens per session scan A 66196628a038

Subscribe to this mod's changes

onboard is a command published in the GitHub repository dtsola/xiaoyaoprivatebill (109 stars, last pushed 16d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.