A closing procedure for finishing a coding task or work session with an audited diff, a focused commit, and a handoff record.

It helps audit changes with an adversarial reviewer, search for related bugs, stage only the relevant files, create a descriptive commit, update project state, and document verification and next steps.

It reduces the chance of shipping known bugs, committing someone else's changes, or making the next session repeat work that was already done.

loop-close — Skill for Claude Code by cbdreamer11

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 cbdreamer11/CB-loop-kit-claude-plugin --skill loop-close

Clone the repo

git clone --depth 1 https://github.com/cbdreamer11/CB-loop-kit-claude-plugin

Made for: Claude Code.

Or install loop-kit, the plugin that ships this one along with the rest of its 7 skills, 6 agents, 2 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close/github.svg)](https://agentmods.dev/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close)

Your own site

<a href="https://agentmods.dev/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close"><img src="https://agentmods.dev/badge/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close"><img src="https://agentmods.dev/badge/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-close.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 630 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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00630
Opus 5.5	$0.00017	$0.00252
Sonnet 5.5	$0.00008	$0.00126
Haiku 4.5	$0.00004	$0.00063

Measured 1mo ago against content hash 6981045ea0d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

loop-close 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.

skills/loop-close/SKILL.md · 57 lines

How it starts

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

Close

Closing is not paperwork. It is the step that makes the next session cheap and stops the same work from being done twice.

1 · Audit before you close

Dispatch the loop-auditor agent on the full diff, with the item's non-negotiables from .loop/STATE.md. Its job is to refute. Iterate until there are zero CONFIRMED findings — and do that before anything is published, not after.

If the auditor finds a real bug, also look for the class of that bug: search for its siblings elsewhere in the codebase and close them in the same session, or record them as their own items. One fixed instance and three live ones is not a fix.

2 · Commit

Stage only your own files. Never git add -A when someone else has uncommitted work in the tree.
A descriptive message: what changed and why, not "fixes".
On the working branch. Never the protected branch — publishing is the owner's action, and it stays that way even when it is obviously fine.
Team mode: open the pull request, make sure CI is green, assign a reviewer. Done means merged, not "it works on my machine".

3 · Write the record

.loop/STATE.md — item to [x] plus one line of what was verified and how. Anything unverified becomes GAP: <why>. Anything blocked becomes PARKED: <why> + exactly what is missing.
.loop/DECISIONS.md — any real choice made, with the rejected alternative.
.loop/GOTCHAS.md — anything that fooled you: the symptom, why it was convincing, and how to detect it next time. This file is the compound interest of the method.

4 · Report honestly

Three lists, no softening:

Verified — with what you observed for each, in one line.
Gaps — what is not verified and why (a missing access, no browser, no test environment). Never dress a gap as done.
Blocked on the owner — a key, real money, a business or legal decision, or permission to publish. State the exact thing needed, not a vague ask.

If something failed, say it failed and show the output. A report that reads better than the work is the one failure this method cannot recover from.

Read the full file on GitHub · 57 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.

1mo ago First seen · 57 lines · 42 tokens per session scan A 6981045ea0d0

Subscribe to this mod's changes

loop-close is a skill published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 630 once invoked, about $0.0002 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.

Claude Code Commits Developer Workflow Git and workflow Planning agentic-workflow ai-agents claude-code-plugin claude-skills

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

oliver-kriska/claude-elixir-phoenix · 61 tokens

branch-and-worktree-workflow

Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…

cbrock84/headcount · 70 tokens

loop-close