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.
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/commands/trellis/start.mdgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote 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/qingyu321/little-claude/start)<a href="https://agentmods.dev/commands/qingyu321/little-claude/start"><img src="https://agentmods.dev/badge/commands/qingyu321/little-claude/start.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.02624 |
| Opus 5 | $0.00000 | $0.01312 |
| Sonnet 5 | $0.00000 | $0.00525 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
start 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 start — 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Session
Initialize your AI development session and begin working on tasks.
Operation Types
| Marker | Meaning | Executor |
|---|---|---|
[AI] |
Bash scripts or Task calls executed by AI | You (AI) |
[USER] |
Slash commands executed by user | User |
Initialization [AI]
Step 1: Understand Development Workflow
First, read the workflow guide to understand the development process:
cat .trellis/workflow.md
Follow the instructions in workflow.md - it contains:
- Core principles (Read Before Write, Follow Standards, etc.)
- File system structure
- Development process
- Best practices
Step 2: Get Current Context
python3 ./.trellis/scripts/get_context.py
This shows: developer identity, git status, current task (if any), active tasks.
Step 3: Read Guidelines Index
cat .trellis/spec/frontend/index.md # Frontend guidelines
cat .trellis/spec/backend/index.md # Backend guidelines
cat .trellis/spec/guides/index.md # Thinking guides
cat .trellis/spec/unit-test/index.md # Testing guidelines
Important: The index files are navigation — they list the actual guideline files (e.g.,
error-handling.md,conventions.md,mock-strategies.md). At this step, just read the indexes to understand what's available. When you start actual development, you MUST go back and read the specific guideline files relevant to your task, as listed in the index's Pre-Development Checklist.
Step 4: Report and Ask
Report what you learned and ask: "What would you like to work on?"
Task Classification
When user describes a task, classify it:
| Type | Criteria | Workflow |
|---|---|---|
| Question | User asks about code, architecture, or how something works | Answer directly |
| Trivial Fix | Typo fix, comment update, single-line change | Direct Edit |
| Simple Task | Clear goal, 1-2 files, well-defined scope | Quick confirm → Implement |
| Complex Task | Vague goal, multiple files, architectural decisions | Brainstorm → Task Workflow |
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 · 390 lines · 0 tokens per session scan A 2d4259d8d146
start is a command published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 12d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,624 tokens. A static security scan graded it A with 0 findings. It is 100% identical to start, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
discover
Search the Everruns(Dev) API catalog for available operations.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
watch
Live-stream swarm events and agent activity in real time.
triage
../../templates/commands/triage.md.