start

A session-start command that checks project changes, loads handoff notes and scratch files, and finds existing plans. A handoff is a note left by an earlier work session.

In plain words
What is it for?
Use it at the start of a task to review recent commits, the current branch, saved context, and relevant plans.
Why use it?
It makes the current project state visible before work begins and helps detect changes made since the last session.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/sefaertunc/worclaude/start
Clone the repo
git clone --depth 1 https://github.com/sefaertunc/Worclaude

Made for: Claude Code.

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 973 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00016 $0.00973
Opus 5 $0.00008 $0.00487
Sonnet 5 $0.00003 $0.00195
Haiku 4.5 $0.00002 $0.00097

Measured 3d ago against content hash aebcd8c87753, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/commands/start.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The SessionStart hook has already loaded CLAUDE.md, PROGRESS.md, and the most recent session summary into context.

When invoked with arguments, use them as the task focus. Example: /start implement auth module

Arguments: $ARGUMENTS

Your job is to supplement that with drift detection, handoff loading, scratch artifact surfacing, and plan discovery.

1. Drift Detection (SHA-based)

Show what changed since the last session so there are no surprises. Present raw signals only — do NOT interpret or warn.

Prefer SHA-based drift when the most recent session summary records a HEAD SHA in its frontmatter. Otherwise fall back to date-based drift.

Run the helper script as a single command — do not unpack the script body. Bundling avoids per-line permission prompts on multi-line bash with X=$(...) assignments and if/elif blocks.

bash .claude/scripts/start-drift.sh

The script outputs the drift list and the current branch name. Report as:

## Drift Since Last Session
- **X commits** since {SHA or date}
- {one-liner per commit, max 15}

Current branch: {branch name}

If there are 0 commits since the last session, just say:

## Drift Since Last Session
No new commits since last session ({SHA or date}). Branch: {branch name}

Do NOT add commentary like "you should review these" or "there may be conflicts." Just the facts.

2. Read handoff and session summary as distinct artifacts

/end writes two files with disjoint content:

  • Handoff at docs/handoffs/HANDOFF-{branch}-{date}.md — forward- looking only (what's left, decisions pending, where to pick up)
  • Session summary at .claude/sessions/{YYYY-MM-DD-HHMM}-{branch}.md — backward-looking only (what got done, observability)

Read both, keeping their roles distinct. Do not merge their content into a single "last session" blob:

  • Look in docs/handoffs/ for any HANDOFF*.md matching the current branch first, then any other recent handoff. Read the most relevant.
  • The session summary is already loaded by the SessionStart hook — re- reference it for "what got done" but don't re-read it.

Read the full file on GitHub · 117 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. 3d ago First seen · 117 lines · 16 tokens per session scan A aebcd8c87753

Subscribe to this mod's changes

start is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 973 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-31.