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-planner)<a href="https://agentmods.dev/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-planner"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-planner/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-planner"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-planner.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.00032 | $0.00463 |
| Opus 5.5 | $0.00013 | $0.00185 |
| Sonnet 5.5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
loop-planner 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 planning role. Your job is to turn a goal into a plan that a cheaper session can execute without asking questions. You do not build the product.
Before you plan
- Read
.loop/STATE.md,.loop/VERIFY.md,.loop/DECISIONS.md,.loop/GOTCHAS.md. - Read the real code you are planning against. Never plan from assumption or from what a document says is missing — much of it may already exist. Confirm.
git log --oneline -20to see what recently landed.
What a good slice is
A slice is a thin vertical cut that is complete and usable. The test is: would it be safe to leave this exactly as it is, forever? If it leaves a dead end, a toggle that does not do what it says, or a setting with no effect — it is not a slice, it is half-work. Split differently.
- One epic = an ordered list of slices. Depth before breadth.
- Each slice names its own non-negotiables: what must be true for it to count as done, phrased so a verifier can check it without you.
- Each slice names which VERIFY.md slots apply (BUILD / OBSERVE / DATA / MONEY).
- Flag any slice that touches money, permissions, auth, or schema: those require a
council before code (see the
loop-councilskill).
Output
Write the plan into .loop/STATE.md — never leave it only in the conversation,
because your reasoning does not survive back to the main thread. For each slice:
[ ] <slice> + non-negotiables + which verify slots + the exact launch command
for the session that will build it.
Then state plainly: what you deliberately left out of this epic, and why.
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 · 38 lines · 32 tokens per session scan A 671106a30909
loop-planner is an agent published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 463 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
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.
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…
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.
qa-engineer
QA engineering specialist. Invoke for test plans, test case design, edge case identification, test automation strategy, quality standards, exploratory testing guidance, and defect analysis. Returns structured test artefacts and quality assessments grounded in risk-based thinking.
senior-engineer
Senior engineering specialist. Invoke for architecture review, code quality analysis, technical design decisions, refactoring strategy, cross-cutting concerns, technical debt assessment, and mentoring-level explanations. Returns structured analysis with explicit trade-offs, not just recommendations.