Little-Claude: Command for Claude Code

.claude/commands/trellis/onboard.md

onboard is a command for Claude Code from qingyu321/Little-Claude. It costs 0 tokens per session (3,401 once invoked), scanned A, a copy of onboard, Apache-2.0.

An onboarding command that teaches a new team member how the project's AI-assisted development workflow works.

In plain words
What is it for?
Use it to explain the system, commands, workflow examples, and how to customize the project's development guidelines.
Why use it?
It explains the reasons behind the workflow and what can go wrong when steps are skipped, rather than giving only a checklist.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is qingyu321/Little-Claude's own configuration. It tells Claude Code how to work on Little-Claude 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 Little-Claude configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 ./.trellis/scripts/task.py create "Fill spec guidelines" --slug fill-spec-guidelines.

Reuse

Borrowing it

Nothing to install: this file belongs to qingyu321/Little-Claude. 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/qingyu321/Little-Claude/main/.claude/commands/trellis/onboard.md
Clone the repo
git clone --depth 1 https://github.com/qingyu321/Little-Claude

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/qingyu321/little-claude/onboard/github.svg)](https://agentmods.dev/commands/qingyu321/little-claude/onboard)
Your own site
<a href="https://agentmods.dev/commands/qingyu321/little-claude/onboard"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/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/qingyu321/little-claude/onboard"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/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 3,401 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 100% copy Near-identical to another mod 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.03401
Opus 5 $0.00000 $0.01700
Sonnet 5 $0.00000 $0.00680
Haiku 4.5 $0.00000 $0.00340

Measured 9d ago against content hash a5dbd5db094b, 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

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.

.claude/commands/trellis/onboard.md · 359 lines

How it starts

The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior developer onboarding a new team member to this project's AI-assisted workflow system.

YOUR ROLE: Be a mentor and teacher. Don't just list steps - EXPLAIN the underlying principles, why each command exists, what problem it solves at a fundamental level.

CRITICAL INSTRUCTION - YOU MUST COMPLETE ALL SECTIONS

This onboarding has THREE equally important parts:

PART 1: Core Concepts (Sections: CORE PHILOSOPHY, SYSTEM STRUCTURE, COMMAND DEEP DIVE)

  • Explain WHY this workflow exists
  • Explain WHAT each command does and WHY

PART 2: Real-World Examples (Section: REAL-WORLD WORKFLOW EXAMPLES)

  • Walk through ALL 5 examples in detail
  • For EACH step in EACH example, explain:
    • PRINCIPLE: Why this step exists
    • WHAT HAPPENS: What the command actually does
    • IF SKIPPED: What goes wrong without it

PART 3: Customize Your Development Guidelines (Section: CUSTOMIZE YOUR DEVELOPMENT GUIDELINES)

  • Check if project guidelines are still empty templates
  • If empty, guide the developer to fill them with project-specific content
  • Explain the customization workflow

DO NOT skip any part. All three parts are essential:

  • Part 1 teaches the concepts
  • Part 2 shows how concepts work in practice
  • Part 3 ensures the project has proper guidelines for AI to follow

After completing ALL THREE parts, ask the developer about their first task.


CORE PHILOSOPHY: Why This Workflow Exists

AI-assisted development has three fundamental challenges:

Challenge 1: AI Has No Memory

Every AI session starts with a blank slate. Unlike human engineers who accumulate project knowledge over weeks/months, AI forgets everything when a session ends.

The Problem: Without memory, AI asks the same questions repeatedly, makes the same mistakes, and can't build on previous work.

The Solution: The .trellis/workspace/ system captures what happened in each session - what was done, what was learned, what problems were solved. The /trellis:start command reads this history at session start, giving AI "artificial memory."

Read the full file on GitHub · 359 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 · 359 lines · 0 tokens per session scan A a5dbd5db094b

Subscribe to this mod's changes

onboard is a command published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,401 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.