close-out-the-run

close-out-the-run is a skill for Claude Code from haiggoh/run-to-completion. It costs 97 tokens per session (748 once invoked), scanned A, original, MIT.

A closing procedure for an unattended software or research run. It checks the records and work touched during the run, then leaves a clear handoff for anything that could not be completed.

In plain words
What is it for?
Use it when an automated run is ending, resources are nearly used up, or the user asks it to stop, so completed items are reconciled and remaining work is documented.
Why use it?
It prevents finished work from being left marked as pending and avoids continuing into tasks that require a person’s decision or approval. It makes the stopping point understandable and recoverable.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the run-to-completion plugin — 6 skills, 1 hook shipped together

Good fit Use it when an automated run is ending, resources are nearly used up, or the user asks it to stop, so completed items are reconciled and remaining work is documented.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/haiggoh/run-to-completion/close-out-the-run
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.

Any agent
npx skills add haiggoh/run-to-completion --skill close-out-the-run
Clone the repo
git clone --depth 1 https://github.com/haiggoh/run-to-completion

Made for: Claude Code.

Or install run-to-completion, the plugin that ships this one along with the rest of its 6 skills, 1 hook.

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

agentmods badge for close-out-the-run

README.md
[![agentmods](https://agentmods.dev/badge/skills/haiggoh/run-to-completion/close-out-the-run/github.svg)](https://agentmods.dev/skills/haiggoh/run-to-completion/close-out-the-run)
Your own site
<a href="https://agentmods.dev/skills/haiggoh/run-to-completion/close-out-the-run"><img src="https://agentmods.dev/badge/skills/haiggoh/run-to-completion/close-out-the-run/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for close-out-the-run

Your own site · 80×15
<a href="https://agentmods.dev/skills/haiggoh/run-to-completion/close-out-the-run"><img src="https://agentmods.dev/badge/skills/haiggoh/run-to-completion/close-out-the-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 748 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00097 $0.00748
Opus 5 $0.00048 $0.00374
Sonnet 5 $0.00019 $0.00150
Haiku 4.5 $0.00010 $0.00075

Measured 4d ago against content hash 725b13135936, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

close-out-the-run 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.

skills/close-out-the-run/SKILL.md · 52 lines

How it starts

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

close-out-the-run — reconcile and leave a clean seam

The run is ending. Your job is to ensure the state is accurate and the handoff is clear.

The two triggers

Close out when:

  1. Clean bounded autonomous work is exhausted (everything left is gated).
  2. The resource you are spending is nearly gone.

Do not churn at the gated boundary

Attempting gated work unsupervised is the single worst way to end a run. It produces low-confidence output that a human must now audit. Stopping is the correct move. State it as a result, not an apology.

Reconcile durable records

Before stopping, check every item the run touched:

  • Every item carries an accurate done state and a resolution title that says what actually happened.
  • Repositories are committed and pushed, and anything the run shipped went through the whole ship loop in execute-unattended — tagged, released where that was appropriate, and dogfooded — rather than being called done at the push. “The tests passed” is weaker than having run the new behaviour once for real, so if the run stopped early at a step, name the step.
  • Plans and notes agree with reality.
  • Nothing is left orphaned or still flagged as pending when it is finished.

A historical record of a completion is worth keeping. A stale pending flag on finished work is a defect to fix. They look similar and are not the same.

Leave a clean seam

Pause any persistent goal or session-continuation mechanism. Do not leave it running against work you have decided not to do.

The final wrap

The wrap has a required shape:

  1. What closed, what advanced, what shipped.
  2. What the run consumed.
  3. A GATED list: Every remaining item with the reason it could not be done autonomously (needs user input, needs a supervised session, needs a download, is a design/taste decision, needs a fresh session) and the concrete next action that would unblock it. Order this list cheapest-to-release first, and carry whatever ungate tier triage recorded — that ordering is what makes the list answerable in one sitting rather than merely readable. Say separately which items are attended-only and which are waiting on a recurring external condition; neither is a failure to unblock.

Read the full file on GitHub · 52 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. 4d ago Changed 725b13135936
  2. 10d ago First seen · 52 lines · 97 tokens per session scan A f492fdd0a68e

Subscribe to this mod's changes

close-out-the-run is a skill published in the GitHub repository haiggoh/run-to-completion (1 stars, last pushed 4d ago), licensed MIT. It adds 97 tokens to every session and 748 once invoked, about $0.0005 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.