Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tincopper/neekonpx agentmods add commands/tincopper/neeko/trellis-continueWrote 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/tincopper/neeko/trellis-continue)<a href="https://agentmods.dev/commands/tincopper/neeko/trellis-continue"><img src="https://agentmods.dev/badge/commands/tincopper/neeko/trellis-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.
<a href="https://agentmods.dev/commands/tincopper/neeko/trellis-continue"><img src="https://agentmods.dev/badge/commands/tincopper/neeko/trellis-continue.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.00517 |
| Opus 5.5 | $0.00000 | $0.00207 |
| Sonnet 5.5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
trellis-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 1mo 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
83% identical to continue — 13 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.
What it actually says
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:
status=planning+ noprd.md→ 1.1 (loadtrellis-brainstorm)status=planning+prd.mdexists +implement.jsonlnot curated (only the seed_examplerow) → 1.3status=planning+prd.md+ curatedimplement.jsonl→ 1.4 (runtask.py startto enter Phase 2)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 output exists (e.g.,prd.mdfor 1.1;implement.jsonlwith curated entries for 1.3) — skip them- 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 omp
Follow the loaded instructions. After each [required] step completes, move to the next.
Reference
Full workflow, skill routing table, and the DO-NOT-skip table live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.
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.
- 1mo ago First seen · 56 lines · 0 tokens per session scan A 23451ac013fb
trellis-continue is a command published in the GitHub repository tincopper/neeko (12 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 517 tokens. A static security scan graded it A with 0 findings. It is 83% identical to continue, differing in 13 lines, and is treated as a copy.
Other commands, from other repositories
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.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.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs.
speckit.specify
Create or update the feature specification from a natural language feature description.