A command for resuming the current task at the appropriate point in the Trellis workflow, a documented sequence for planning, building, and finishing work.

Use it to inspect the task state and route the next step, such as research, planning review, implementation, or finishing.

It shows the current task, workflow phase, and saved files so you do not have to remember where work stopped.

continue — Command by mjwyr

Install

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.

agentmods

npx agentmods add commands/mjwyr/mysql_mcp_plus/continue

Clone the repo

git clone --depth 1 https://github.com/mjwyr/mysql_mcp_plus

Made for: Claude Code.

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 588 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 95% 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00588
Opus 5	$0.00000	$0.00294
Sonnet 5	$0.00000	$0.00118
Haiku 4.5	$0.00000	$0.00059

Measured 2d ago against content hash eade769e4661, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

This is a copy

95% identical to continue — 8 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/continue.md · 57 lines

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

python ./.trellis/scripts/get_context.py

Confirms: current task, git state, recent commits.

Step 2: Load the Phase Index

python ./.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 + no prd.md → 1.1 (load trellis-brainstorm)
status=planning + prd.md only → decide whether the task is lightweight or complex. Lightweight can move to 1.4 review; complex returns to 1.1 to add design.md + implement.md.
status=planning + complex artifacts complete + sub-agent jsonl not curated (only the seed _example row) → 1.3
status=planning + required artifacts complete + required jsonl curated or inline mode → 1.4 (ask for start review; only run task.py start after user confirms)
status=in_progress + implementation not started → 2.1
status=in_progress + implementation done, not yet checked → 2.2
status=in_progress + check passed → 3.3 (spec update) → 3.4 (commit)
status=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.md alone can be enough only for lightweight tasks; complex tasks also need design.md and implement.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:

python ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform claude

Read the full file on GitHub · 57 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.

2d ago First seen · 57 lines · 0 tokens per session scan A eade769e4661

Subscribe to this mod's changes

continue is a command published in the GitHub repository mjwyr/mysql_mcp_plus (0 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 588 tokens. A static security scan graded it A with 0 findings. It is 95% identical to continue, differing in 8 lines, and is treated as a copy.

Planning Productivity

continue

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Continue Current Task

Step 1: Load Current Context

Step 2: Load the Phase Index

Step 3: Decide Where You Are

Step 4: Load the Specific Step

What this file has done since we first saw it

Other commands, from other repositories

minutes-ideas

autobot-result

engage.actions

version

thread

handoff