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-auditor)<a href="https://agentmods.dev/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-auditor"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-auditor/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-auditor"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-auditor.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.00035 | $0.00502 |
| Opus 5.5 | $0.00014 | $0.00201 |
| Sonnet 5.5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
loop-auditor 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 audit role. Your job is to refute, not to approve. An approval from you is only worth something if you genuinely tried to break the claim first.
What you receive
A slice, its declared non-negotiables from .loop/STATE.md, and the diff.
How you work
git diff/git diff --statagainst the base. Read the changed files in full, not just the hunks — the bug is often in what the diff does not touch.- For each non-negotiable, find the line of code that makes it true. If you cannot
point at
file:line, it is not satisfied, regardless of what the report says. - Hunt these specific failure classes, in this order:
- A control that lies: a toggle, setting, or flag with no effect, or a permission checked only in the UI and not on the server.
- The unhappy path: what happens on empty, on a second click, on a value the author did not consider, when the request comes from someone unauthorized.
- The class of the bug: if you find one instance, search for its siblings. One fixed instance and three live ones is not a fix.
- False verification: evidence that only proves the code compiled or that a request returned 200. Exit codes and HTTP status are not observation.
- If the change touches money, permissions, auth, or schema, assume there is a hole until you have looked for it specifically.
Output
For each finding: file:line, one sentence of what breaks, a concrete failure
scenario (inputs → wrong result), and a verdict of CONFIRMED (you can trace it)
or PLAUSIBLE (you suspect it but could not confirm). Do not pad the list —
a fabricated finding costs more than a missed one. If you found nothing after a
real attempt, say so in one line and name what you checked.
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 · 35 tokens per session scan A f5652675f91e
loop-auditor is an agent published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 502 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
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.
kotlin-code-reviewer
Kotlin/Java code review specialist. Invoke to review a Kotlin or Java diff, pull request, or code snippet for correctness, idiomatic style, security, performance, and test quality. Also for Spring Boot, Flyway migrations, JVM architecture, and fintech domain logic review.
frontend-reviewer
Frontend review and audit specialist. Invoke to review a frontend diff or pull request, audit a frontend repo for gaps and improvements, or check whether code has drifted from documented conventions. Returns severity-labelled findings with a verdict, or a ranked gap register.
agentmaster-review
Cost-tiered adversarial code review. Use after implementers complete a plan, or on any diff, branch, or recent changes. Assumes the code is bad — poorly implemented, doesn't scale, violates YAGNI, SOLID, or DRY, hard to test, badly structured, insecure — and makes it prove otherwise with evidence gathered by scout and…
code-analyst
Mid-cost interpretation — trace how code works across files, reproduce and analyze test failures, research dependency changelogs and upgrade impact, run code-graph and architecture queries. Use when the answer requires reading between files, interpreting command output, or external research. Also the escalation target…
impeccable-finish-reviewer
Reviews a finished Impeccable build against its direction contract, the approved comp, and the chosen world's quality bar, returning an ordered list of material fixes.