Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/yuqie6/productflow/continuegit clone --depth 1 https://github.com/yuqie6/ProductFlowWhat 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 | $0.00000 | $0.00578 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
continue 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 2d 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
5 near-identical copies found in the catalogue:
- continue — 95% identical, 8 lines differ
- trellis-continue — 95% identical, 8 lines differ
- continue — 95% identical, 8 lines differ
- continue — 95% identical, 2 lines differ
- trellis-continue — 83% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Current Task
Resume work on the current task — pick up at the right phase/step in .trellis/workflow.md.
Step 1: Load Current Context
python3 ./.trellis/scripts/get_context.py
Confirms: current task, git state, recent commits.
Step 2: Load the Phase Index
python3 ./.trellis/scripts/get_context.py --mode phase
Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.
Step 3: Decide Where You Are
get_context.py shows the active task's status field. Route by status + artifact presence. This command replaces the user needing to remember the Trellis flow; it does not itself approve implementation.
status=planning+ noprd.md→ 1.1 (loadtrellis-brainstorm)status=planning+prd.mdonly → decide whether the task is lightweight or complex. Lightweight can move to 1.4 review; complex returns to 1.1 to adddesign.md+implement.md.status=planning+ complex artifacts complete + sub-agent jsonl not curated (only the seed_examplerow) → 1.3status=planning+ required artifacts complete + required jsonl curated or inline mode → 1.4 (ask for start review; only runtask.py startafter user confirms)status=in_progress+ implementation not started → 2.1status=in_progress+ implementation done, not yet checked → 2.2status=in_progress+ check passed → 3.1status=completed(rare; usually archived immediately) → archive flow
Phase rules (full detail in .trellis/workflow.md):
- Run steps in order within a phase —
[required]steps must not be skipped [once]steps are already done if the required output exists.prd.mdalone can be enough only for lightweight tasks; complex tasks also needdesign.mdandimplement.md.- You may go back to an earlier phase if discoveries require it
Step 4: Load the Specific Step
Once you know which step to resume at:
python3 ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform claude
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.
- 2d ago First seen · 57 lines · 0 tokens per session scan A 78bea91cc54b
continue is a command published in the GitHub repository yuqie6/ProductFlow (301 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 578 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.
Other commands, from other repositories
triage
Triage Linear issue with comprehensive analysis.
os-meeting
快速创建和管理AI团队会议.
card
Open one self-contained OverClick card.
bmad-cis-agent-creative-problem-solver
Master problem solver for systematic problem-solving methodologies. Use when the user asks to talk to Dr. Quinn or requests the Master Problem Solver.
bmad-cis-design-thinking
Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking".
verify
Run the full local verification the way CI does, and report pass/fail for each step.