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 skills add haiggoh/run-to-completion --skill close-out-the-rungit clone --depth 1 https://github.com/haiggoh/run-to-completionWrote 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/haiggoh/run-to-completion/close-out-the-run)<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.
<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>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.1 | $0.00097 | $0.00795 |
| Opus 5.5 | $0.00039 | $0.00318 |
| Sonnet 5.5 | $0.00019 | $0.00159 |
| Haiku 4.5 | $0.00010 | $0.00080 |
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 1mo 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 — 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:
- Clean bounded autonomous work is exhausted (everything left is gated).
- 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— landed on the branch consumers resolve, tagged, released where that was appropriate, and dogfooded — rather than being called done at the push. Work left sitting on an unmerged branch is a specific thing to look for: it is fully committed and pushed, so it reads as finished from the repository side while remaining unobtainable by anyone. “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:
- What closed, what advanced, what shipped.
- What the run consumed.
- 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.
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.
- 1mo ago Changed 7af810234d7e
- 1mo ago Changed 725b13135936
- 1mo ago First seen · 52 lines · 97 tokens per session scan A f492fdd0a68e
close-out-the-run is a skill published in the GitHub repository haiggoh/run-to-completion (1 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 795 once invoked, about $0.0004 per session on Opus 5.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
build-workflow
Full 3-phase pipeline (Research → Write+Validate → Deploy+Test) for shipping an n8n workflow end-to-end. Wraps Etienne's n8n-as-code:n8n-architect skill for schema research + authoring, adds repo-scoped orchestration — community-template lookup, validate-push-test loop, mcpTrigger publish gate, execution inspection…
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.
scout-dream
Launch a Scout dreaming session as a background process. Processes feedback, does KB deep work, and works on wishlist items.
collaboration
Use for /collaboration, collaboration repair, friction signals, soft-skills coaching, or structured human-Claude interaction techniques such as compromise, rubber ducking, energy checks, pairing, retros, working agreements, and perspective swaps.
therapist
Run a structured human-Claude collaboration retrospective. Use for /therapist, therapy sessions, interaction reviews, workflow check-ins, frustration recovery, or improving how the user and Claude work together.