agentmods.dev

yaicli: Command for Claude Code

.claude/commands/trellis/continue.md

continue is a command for Claude Code from belingud/yaicli. It costs 0 tokens per session (595 once invoked), scanned A, a copy of continue, Apache-2.0.

A command for continuing an unfinished task by reading the project's workflow and current task status.

In plain words
What is it for?
Use it when returning to work to determine whether to plan, review, research, implement, or perform another workflow step.
Why use it?
It helps you resume at the correct step without manually reconstructing the task's progress.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is belingud/yaicli's own configuration. It tells Claude Code how to work on yaicli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything yaicli configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 ./.trellis/scripts/get_context.py.

not rated 19repo yesterday A scan 0 tokens copy · 92% Apache-2.0
View source ↗ belingud/yaicli belingud.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to belingud/yaicli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/belingud/yaicli/master/.claude/commands/trellis/continue.md
Clone the repo
git clone --depth 1 https://github.com/belingud/yaicli

Made for: Claude Code.

Wrote 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.

agentmods badge for continue

README.md
[![agentmods](https://agentmods.dev/badge/commands/belingud/yaicli/continue/github.svg)](https://agentmods.dev/commands/belingud/yaicli/continue)
Your own site
<a href="https://agentmods.dev/commands/belingud/yaicli/continue"><img src="https://agentmods.dev/badge/commands/belingud/yaicli/continue/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.

agentmods 80×15 button for continue

Your own site · 80×15
<a href="https://agentmods.dev/commands/belingud/yaicli/continue"><img src="https://agentmods.dev/badge/commands/belingud/yaicli/continue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00595
Opus 5.5 $0.00000 $0.00238
Sonnet 5.5 $0.00000 $0.00119
Haiku 4.5 $0.00000 $0.00060

Measured 5d ago against content hash 4ed3a1ca2fe5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 5d 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

92% identical to continue — 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.

.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

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 + 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 (empty, or only a legacy _example placeholder 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):

  1. Run steps in order within a phase — [required] steps must not be skipped
  2. [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.
  3. 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:

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.

  1. 5d ago First seen · 57 lines · 0 tokens per session scan A 4ed3a1ca2fe5

Subscribe to this mod's changes

continue is a command published in the GitHub repository belingud/yaicli (19 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 595 tokens. A static security scan graded it A with 0 findings. It is 92% identical to continue, differing in 4 lines, and is treated as a copy.

LLMPlanningPythonchatgptcligpttyper
Related

continue compared with commands from other repositories

continue next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
continuebelingud/yaicliCommand19yesterdayApache-2.0A0Claude Code
AGENTSlanggenius/difyCommand160kyesterdaynoneA0Claude Code
modernize-extract-rulesronmkr/PromptBookCommand25mo agoApache-2.0A14Claude Code
modernize-transformronmkr/PromptBookCommand25mo agoApache-2.0A17Claude Code
helpronmkr/PromptBookCommand25mo agoApache-2.0D7Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code