Borrowing it
Nothing to install: this file belongs to yuqie6/ProductFlow. 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/yuqie6/ProductFlow/main/.agents/skills/trellis-start/SKILL.mdgit clone --depth 1 https://github.com/yuqie6/ProductFlowWrote 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/skills/yuqie6/productflow/trellis-start)<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-start"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/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/skills/yuqie6/productflow/trellis-start"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.00668 |
| Opus 5 | $0.00036 | $0.00334 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- trellis-start — 100% identical, 8 lines differ
- trellis-start — 100% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Session
Initialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent compact context by following these steps.
Step 1: Current state
Identity, git status, current task, active tasks, journal location.
python3 ./.trellis/scripts/get_context.py
If this output includes a line beginning Trellis update available:, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.
Step 2: Workflow overview
Compact Phase Index, request triage rules, planning artifact contract, and the step-detail command.
python3 ./.trellis/scripts/get_context.py --mode phase
Full guide in .trellis/workflow.md (read on demand).
Step 3: Guideline indexes
Discover packages + spec layers, then read each relevant index file.
python3 ./.trellis/scripts/get_context.py --mode packages
cat .trellis/spec/guides/index.md
cat .trellis/spec/<package>/<layer>/index.md # for each relevant layer
Index files list the specific guideline docs to read when you actually start coding.
Step 4: Decide next action
From Step 1 you know the current task and status. Check the task directory:
- Active task status
planning+ noprd.md→ Phase 1.1. Load thetrellis-brainstormskill. - Active task status
planning+prd.mdexists → stay in Phase 1. Lightweight tasks can be PRD-only; complex tasks needdesign.md+implement.md. Load the relevant Phase 1 step detail beforetask.py start. - Active task status
in_progress→ Phase 2 step 2.1. Load the step detail:python3 ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex - No active task → classify first. For simple conversation / small task, ask only whether this turn should create a Trellis task. For complex work, ask whether you may create a Trellis task and enter planning. If the user says no, skip Trellis for this session.
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.
- 9d ago First seen · 65 lines · 73 tokens per session scan A 79a5ba7a2aff
trellis-start is a skill published in the GitHub repository yuqie6/ProductFlow (302 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 668 once invoked, about $0.0004 per session on Opus 5. 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.
Other skills, from other repositories
spec-generate
Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step workflow. Output in English Markdown format.
post-merge-cleanup
Finish an already-merged branch. Proves the branch is contained in the fetched default, classifies leftover artifacts as unique / redundant / superseded, returns to a clean --ff-only default checkout, and deletes the merged local branch — every discard confirmed per item. Routed to by {{CMD:cleanup}}.
release
A release workflow for a desktop application that updates its version, writes release notes, and opens the release pull request.
dev-todo-mode
A task-execution format for software requests received through Telegram. It presents a short plan, reports progress after each stage, and ends with changed files and verification results.
telegram-announce
Purpose.
git-push-workflow
This skill should be used when the user says "push", "push to remote", "create PR", "create MR", "pull request", "merge request", "open PR", or when committing and pushing code to GitHub or GitLab. Covers git workflow rules, branch naming conventions, commit message format, and the push + PR/MR creation procedure.