Borrowing it
Nothing to install: this file belongs to qxchuckle/qcqx-project-manage. 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/qxchuckle/qcqx-project-manage/master/.cursor/commands/trellis-start.mdgit clone --depth 1 https://github.com/qxchuckle/qcqx-project-manageWrote 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/qxchuckle/qcqx-project-manage/trellis-start)<a href="https://agentmods.dev/commands/qxchuckle/qcqx-project-manage/trellis-start"><img src="https://agentmods.dev/badge/commands/qxchuckle/qcqx-project-manage/trellis-start/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.
<a href="https://agentmods.dev/commands/qxchuckle/qcqx-project-manage/trellis-start"><img src="https://agentmods.dev/badge/commands/qxchuckle/qcqx-project-manage/trellis-start.svg" alt="Reviewed on agentmods" width="80" 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.02263 |
| Opus 5 | $0.00000 | $0.01131 |
| Sonnet 5 | $0.00000 | $0.00453 |
| Haiku 4.5 | $0.00000 | $0.00226 |
Grade A, and why
trellis-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 10d 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
91% identical to trellis-start — 4 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 — 371 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
Operations in this document are categorized as:
| Marker | Meaning | Executor |
|---|---|---|
[AI] |
Bash scripts or file reads executed by AI | You (AI) |
[USER] |
Slash commands executed by user | User |
Initialization
Step 1: Understand Trellis Workflow [AI]
First, read the workflow guide to understand the development process:
cat .trellis/workflow.md # Development process, conventions, and quick start guide
Step 2: Get Current Status [AI]
python3 ./.trellis/scripts/get_context.py
This returns:
- Developer identity
- Git status (branch, uncommitted changes)
- Recent commits
- Active tasks
- Journal file status
Step 3: Read Project Code-Spec Index [AI]
Based on the upcoming task, read appropriate code-spec docs:
For Frontend Work:
cat .trellis/spec/frontend/index.md
For Backend Work:
cat .trellis/spec/backend/index.md
For Cross-Layer Features:
cat .trellis/spec/guides/index.md
cat .trellis/spec/guides/cross-layer-thinking-guide.md
Step 4: Check Active Tasks [AI]
python3 ./.trellis/scripts/task.py list
If continuing previous work, review the task file.
Step 5: Report Ready Status and Ask for Tasks
Output a summary:
## Session Initialized
| Item | Status |
|------|--------|
| Developer | {name} |
| Branch | {branch} |
| Uncommitted | {count} file(s) |
| Journal | {file} ({lines}/2000 lines) |
| Active Tasks | {count} |
Ready for your task. 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, < 5 minutes | Direct Edit |
| Simple Task | Clear goal, 1-2 files, well-defined scope | Quick confirm → Task Workflow |
| 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.
- 10d ago First seen · 371 lines · 0 tokens per session scan A 7244d7fed340
trellis-start is a command published in the GitHub repository qxchuckle/qcqx-project-manage (4 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,263 tokens. A static security scan graded it A with 0 findings. It is 91% identical to trellis-start, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.