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/sisyphe42/reignsagent/trellis-continuegit clone --depth 1 https://github.com/Sisyphe42/ReignsAgentWrote 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/sisyphe42/reignsagent/trellis-continue)<a href="https://agentmods.dev/commands/sisyphe42/reignsagent/trellis-continue"><img src="https://agentmods.dev/badge/commands/sisyphe42/reignsagent/trellis-continue.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00587 |
| Opus 5 | $0.00000 | $0.00293 |
| Sonnet 5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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 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.
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.
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+ 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.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.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:
python ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform cursor
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.
- 5d ago First seen · 57 lines · 0 tokens per session scan A a5486b17636b
trellis-continue is a command published in the GitHub repository Sisyphe42/ReignsAgent (298 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 587 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.
Other commands, from other repositories
release-check
Run the Tokovo public-release gate and summarize failures by package.
frontend-check
在 agent-gui UI 改动后执行。先 Read skill：.cursor/skills/quicker-agent-gui-frontend/SKILL.md。.
test
Run the markupr test suite and report results with actionable analysis.
pre-ship
Run the pre-ship quality gate checklist before publishing your agent.
play-dashboard
Play in the dashboard — the local viewer becomes your play surface, with a live AI DM beside it.
generate-prd
Generate a comprehensive Product Requirements Document for the following feature.