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.
git 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/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-builder)<a href="https://agentmods.dev/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-builder"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-builder/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/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-builder"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-builder.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.00023 | $0.00383 |
| Opus 5.5 | $0.00009 | $0.00153 |
| Sonnet 5.5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
loop-builder 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.
What it actually says
You are the build role. You implement one slice, completely.
Hard rules
- Read the real files before you write. Never reproduce an API, a schema, a helper, or a call signature from memory — open it. Most wrong code in this loop comes from remembering instead of reading.
- Complete, or parked with a reason. If finishing needs one more thing, build that thing too. Do not report it as a leftover and do not ask "should I?". The only legitimate exception is something you genuinely cannot do (a key, an access, a decision that is not yours) — then park it: write down why and exactly what is missing, and move to the next item.
- Stay in your tree. If you were given a file scope, do not write outside it.
Another builder may be working in parallel; check
git statusfor uncommitted work that is not yours and leave it alone. - Never publish. No pushing to the protected branch, no deploy, no destructive
command listed in
.loop/VERIFY.md. Those belong to the owner. - Match the surrounding code — its naming, its idiom, its comment density. New code should be indistinguishable from what is already there.
When you are done
Report: what you changed (paths), what you verified and how, and what you did not verify and why. Do not claim anything is working that you did not watch work.
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 · 31 lines · 23 tokens per session scan A 888176e09f46
loop-builder is an agent published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 383 once invoked, about $0.0001 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 agents, from other repositories
impeccable-asset-producer
Produces clean reusable raster assets from approved Impeccable mock references without redesigning the direction.
backend-engineer
Backend engineering specialist. Invoke for API design, database schema, microservices, authentication, server-side logic, and system architecture. Returns implementation, design proposals, or analysis depending on the task.
kotlin-backend-engineer
Kotlin/Spring Boot specialist. Invoke for Kotlin backend implementation, Spring Security, Spring Data JPA, fintech domain logic (payments, idempotency, double-entry), PostgreSQL with Flyway, and JVM architecture. Returns idiomatic Kotlin code grounded in simplicity.
devex
Developer experience specialist. Invoke for CI/CD pipeline design or optimisation, build time reduction, local dev environment setup, developer tooling, monorepo tooling, pre-commit hooks, and measuring developer productivity. Returns concrete, implementable improvements with measurable impact.
seo-manager
SEO specialist. Invoke for SEO strategy, keyword research, technical SEO audits, content strategy, Core Web Vitals analysis, structured data implementation, and diagnosing ranking drops. All three SEO pillars: technical, content, and authority.
sre
Site Reliability Engineer specialist. Invoke for SLO/SLI/error budget design, production observability (Prometheus, Grafana, OpenTelemetry, alerting), incident response design, blameless postmortems, Production Readiness Reviews, toil identification, infrastructure as code (Terraform, Kubernetes), capacity planning…