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/loopnpx skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loopgit clone --depth 1 https://github.com/cbdreamer11/CB-loop-kit-claude-pluginWhat 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.00048 | $0.00926 |
| Opus 5 | $0.00024 | $0.00463 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
loop 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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The loop
Nothing is done until it has been observed working. A green build, "I read the code and it looks right", and "this should work" are not verification. The only valid signal is observed behaviour.
Run these six steps for every item. Do not skip 0 and do not skip 5.
0 · Locate yourself
- Read
.loop/STATE.md(what is done, what is next, what is parked) and.loop/GOTCHAS.md(traps this project has already sprung). git log --oneline -15andgit status. Anything already committed is not rebuilt. A lot of what a document calls missing is already built and just not visible — confirm against the code before redoing it.- Uncommitted files that are not yours may belong to a parallel session. Do not
touch them, and do not reuse a shared counter they may have taken (see the shared
resource in
.loop/VERIFY.md— read its true state with the command declared there). - The next item is the first unchecked
[ ]in.loop/STATE.md. You do not need new instructions to continue.
1 · Investigate
Open the real files you are about to change. Map what exists, what is editable,
what is missing. Never work from memory of an API or a schema.
If a question is genuinely open — or the item touches money, permissions, auth, or
schema — run the loop-council skill before writing code, not after.
2 · Build, completely
One item at a time, finished. If completing it requires one more thing, that thing gets built too: it is not reported as a leftover and it is not offered as a question. An item is complete only if it would be safe to leave exactly as it is, forever — no dead end, no control that does not do what it says, no setting with no effect.
3 · Verify for real
Run the slots in .loop/VERIFY.md that apply. The rule for each: it must produce an
artifact or an observation — a rendered page, a row, a file, a screenshot, a log
line that only exists if the new code ran. Forbidden as evidence: an exit code, an
HTTP 200, and "the build passed". Those prove the code compiled, not that it works.
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.
- 2d ago First seen · 72 lines · 48 tokens per session scan A 90fda5b42aba
loop is a skill published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 926 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.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-payments
Agent skill for payments - invoke with $agent-payments.
agui-dotnet-cross-language-tests
Author cross-language interop tests that verify the AG-UI .NET SDK is wire-compatible with the TypeScript SDK — a Vitest TS client driving a C# CrossLanguage.TestServer over HTTP, both directions, including protobuf byte-parity against @ag-ui/proto. USE FOR: adding or modifying cross-language interop coverage…
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…