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/lookatitude/guild/resumegit clone --depth 1 https://github.com/lookatitude/guildWhat 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.00035 | $0.01376 |
| Opus 5 | $0.00017 | $0.00688 |
| Sonnet 5 | $0.00007 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00138 |
Grade A, and why
resume 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 3d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guild:resume — lifecycle helper
Continues the active run from the next pending gate. No phase — acts on the active run.
--restart replaces the v1 first-word $ARGUMENTS --restart hack.
Args & local flags
- Args: — (no positional)
--no-index— per-invocation filesystem-scan bypass of the optional read-through cache (Invariant FS-CANONICAL: filesystem is always the authoritative source).--restart— clears run state and re-runs from Init/Ideation (confirm-before-clear I).
Gates
Resumes at the next I gate. --restart adds a confirm-before-clear I
gate.
Output
Continues the active run's phase artifacts (no new artifact kind introduced).
Run-start preflight (settings-control-and-tmux U3/U6)
resume continues an existing run, so its resolved-settings snapshot is
already on disk — run-trace.js start wrote it at the original run-start (since
wave 2 the run-trace CLI is the sole caller of runStartPreflight;
scripts/lib/runstart-preflight.ts; canonical contract in guild.md §Run-start preflight). Do not re-run the preflight or overwrite the snapshot for the
resumed run: read it back with readResolvedSettingsSnapshot(runId, { cwd }).
Re-enter resumable dead lanes (R-016). Before locating the next pending
gate, list any resumable dead lanes for the active run:
npx tsx ${GUILD_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$HOME/.local/share/guild/dist/claude-code}}/scripts/resume-lanes.ts <runDir> --json (the
--json flag is required for the parseable bare array; without it the CLI
prints a human table — scans
<runDir>/lanes/*/resume.json, applies the guild.lane_resume.v1 version
guard, honors defaults.resume.enabled). For each returned lane, re-enter it
via guild:execute-plan's ## Resuming dead lanes (R-016) path — a fresh
dispatch from the checkpoint with a fresh retry budget (prior attempts are
preserved in the checkpoint for audit, not subtracted). An empty list ⇒ skip
straight to the next step (exactly today's behavior). Then proceed to gate
continuation.
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.
- 3d ago First seen · 116 lines · 35 tokens per session scan A 895fed9252b1
resume is a command published in the GitHub repository lookatitude/guild (7 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,376 once invoked, about $0.0002 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.