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 skills/auerbachb/claude-code-config/end-resumenpx skills add auerbachb/claude-code-config --skill end-resumegit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/skills/auerbachb/claude-code-config/end-resume)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/end-resume"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/end-resume.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.00089 | $0.01356 |
| Opus 5 | $0.00044 | $0.00678 |
| Sonnet 5 | $0.00018 | $0.00271 |
| Haiku 4.5 | $0.00009 | $0.00136 |
Grade A, and why
end-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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume a cost-quiescent /end explicitly. This is the only normal path that
reopens the session-scoped launch gate; unrelated messages and timers do not.
/go-onis the primary entry point for resuming. It classifies the stoppage from recorded evidence and routes here when the newest record is an/end, forwarding--resume-refillverbatim — so nobody has to remember which stop happened (Issue #1397; ladder:.claude/reference/universal-resume.md). This command keeps working unchanged and stays the direct path when you already know the session was ended; it remains the executor, and a routed invocation is still an explicit human invocation of it. Portable handoff documents keep naming/end-resumealone in theirResume command:field — that field is lint-restricted to this command because its reader may be outside this harness entirely.
Step 0: Resolve state helpers
Resolve execution-pause.sh, background-task-registry.sh, and
session-state.sh using the standard stop-command order: skills worktree,
then $HOME/.claude. Do not execute a current-checkout fallback: this command
may be invoked from an unrelated or untrusted repository. Parse only
--resume-refill.
Before clearing the gate, require all three helpers to be resolved and readable.
Use the registry to list the current session and use session-state.sh to read
the repo key/refill state. If either inventory is unavailable or malformed,
report a degraded resume and leave the execution gate closed. If
execution-pause.sh is missing or cannot clear the current
${CLAUDE_SESSION_ID:-default} gate, likewise stop without re-arming anything.
A partial resume behind an unknown or unreadable inventory is worse than a
visible no-op.
Step 1: Clear the execution gate
Call execution-pause.sh --clear --session "$SESSION_ID". This explicit human
invocation authorizes new background starts again. Do not clear the independent
.repos[REPO].refill.paused gate unless --resume-refill was supplied.
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.
- 4d ago First seen · 119 lines · 89 tokens per session scan A 36d509292236
end-resume is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 5d ago), licensed MIT. It adds 89 tokens to every session and 1,356 once invoked, about $0.0004 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 skills, from other repositories
fixer
Surgical code fixer for Bug Hunter. Implements minimal, precise fixes for verified bugs. Uses doc-lookup (Context Hub + Context7) to verify correct API usage in patches. Respects fix strategy classifications (safe-autofix vs manual-review vs larger-refactor).
referee
Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.
do-competitively
Execute tasks through competitive multi-agent generation, meta-judge evaluation specification, multi-judge evaluation, and evidence-based synthesis.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.
judge-with-debate
Evaluate solutions through multi-round debate between independent judges until consensus.