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/xiaolai/cc-suite/continuegit clone --depth 1 https://github.com/xiaolai/cc-suiteWhat 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.00017 | $0.01105 |
| Opus 5 | $0.00009 | $0.00553 |
| Sonnet 5 | $0.00003 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
What This Does
Continues a previous Codex session via codex exec resume (through the CLI runner). The session preserves full context from the original command, so you can:
Note: Codex CLI sessions persist on disk, so they survive Claude Code / shell restarts (unlike the old in-memory MCP threads). A
threadIdfrom an earlier session can still be resumed later. If a session id is genuinely unknown,codex exec resume --lastpicks the most recent; otherwise start fresh with /audit, /implement, or another command.
- Iterate on audit findings: "Now fix the 3 Critical issues you found"
- Follow up on implementation: "Run the tests and fix any failures"
- Drill into bug analysis: "Show me the exact call stack for issue #2"
- Refine a review: "Explain the race condition you flagged in more detail"
Workflow
Step 1: Parse input
Extract the threadId and follow-up prompt from $ARGUMENTS:
| Input | Interpretation |
|---|---|
<threadId> <prompt> |
Thread ID + follow-up message |
<threadId> (no prompt) |
Ask the user for the follow-up prompt |
| (empty) | Ask the user for both threadId and prompt |
ThreadId detection heuristic: Thread IDs are UUID-format strings (e.g., 019d10e8-5bf9-77e2-b518-f5256fa06b2c) or short alphanumeric tokens. The first token in $ARGUMENTS is a threadId if it matches a UUID pattern (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) or is a single alphanumeric string with no spaces. Otherwise, treat the entire input as a prompt and ask for the threadId.
If $ARGUMENTS is empty or missing the threadId:
AskUserQuestion:
question: "What is the thread ID from the previous Codex command?"
header: "Thread ID"
options:
- label: "Paste thread ID"
description: "The threadId shown in the output of your previous command"
- label: "I don't have one"
description: "Start a new session with /audit, /implement, etc. instead"
If the user doesn't have a threadId, suggest they run one of the main commands first and STOP.
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 · 123 lines · 17 tokens per session scan A a7dfc4b6e7b2
continue is a command published in the GitHub repository xiaolai/cc-suite (44 stars, last pushed 24d ago), licensed ISC. It adds 17 tokens to every session and 1,105 once invoked, about $0.0001 per session on Opus 5. 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
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.