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/cbdreamer11/cb-loop-kit-claude-plugin/loop-closenpx skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loop-closegit clone --depth 1 https://github.com/cbdreamer11/CB-loop-kit-claude-pluginWrote 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/cbdreamer11/cb-loop-kit-claude-plugin/loop-close)<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="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.00042 | $0.00630 |
| Opus 5 | $0.00021 | $0.00315 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
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 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 — 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 -Awhen 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 becomesGAP: <why>. Anything blocked becomesPARKED: <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.
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 · 57 lines · 42 tokens per session scan A 6981045ea0d0
loop-close is a skill published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 630 once invoked, about $0.0002 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
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.