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/sefaertunc/worclaude/endgit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/end)<a href="https://agentmods.dev/commands/sefaertunc/worclaude/end"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/end.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.00014 | $0.00958 |
| Opus 5 | $0.00007 | $0.00479 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
end 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this ONLY when stopping work mid-task without committing.
When invoked with arguments, use them as the description of current work. Example: /end implementing user registration
Arguments: $ARGUMENTS
Do NOT update PROGRESS.md — /sync handles that on develop after merging.
Pre-flight: Worktree Safety
If you are working in a git worktree (not the main checkout):
- Check for uncommitted changes:
git status --porcelain - If changes exist, commit or stash before proceeding
- Note which worktree you are in for the handoff file
- Do NOT remove the worktree from /end — the user may resume here
Mid-task handoff
/end writes two artifacts with disjoint content:
- Handoff (
docs/handoffs/HANDOFF-{branch}-{date}.md) — forward-looking only. What's left, decisions still pending, where to pick up. Do NOT include what got done or workflow observability — those belong in the session summary. - Session summary (
.claude/sessions/{YYYY-MM-DD-HHMM}-{branch}.md) — backward-looking only. What got done, files modified, agents invoked, commands used, verification result. Do NOT include "what's left" — that belongs in the handoff.
The split is deliberate: handoffs answer "where does the next session start?", session summaries answer "what happened in this session?". Mixing them makes both harder to consume.
Steps
-
Create the handoff at
docs/handoffs/HANDOFF-{branch-name}-{date}.md:- What's left to do — concrete next steps, in priority order
- Decisions still pending — items that need a human call before the next session can pick them up
- Where to pick up — exact file/line/command to start with, plus any
scratch artifacts (
.claude/scratch/last-review.md, etc.) that are SHA-relevant - Open questions — anything ambiguous that the next session needs to resolve before continuing
-
git add -A -
git commit -m "wip: handoff for [task description]"Use exactly this message format — no trailers or Co-Authored-By lines.
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 · 94 lines · 14 tokens per session scan A 82a36d292f05
end is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 24d ago), licensed MIT. It adds 14 tokens to every session and 958 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.
Other commands, from other repositories
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.