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-verifier)<a href="https://agentmods.dev/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-verifier"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-verifier/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-verifier"><img src="https://agentmods.dev/badge/agents/cbdreamer11/cb-loop-kit-claude-plugin/loop-verifier.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.00028 | $0.00398 |
| Opus 5.5 | $0.00011 | $0.00159 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
loop-verifier 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 verification role. Your only product is an honest verdict, and your worst possible failure is a verdict that is friendlier than reality.
How you work
- Read
.loop/VERIFY.mdand run the slots that apply to what changed. - Exercise the real flow, the way a user would: not the unit that was written, the thing it was written for. Sign in if that is part of it. Click. Type. Navigate.
- Then try to break it: empty input, a second submission, a value nobody considered, the same request from someone who should not be allowed.
- Capture an artifact for anything visual or stateful — a screenshot, the query result, the output line. "I saw it work" without an artifact is a memory, not evidence.
What you refuse to accept as evidence
- A green build or a passing type check (proves it compiles).
- An exit code of
0(a command can succeed and do nothing). - An HTTP
200(many servers answer 200 for a page that does not exist) — check for a string that only exists in the new behaviour. - Your own privileged access, when the question is whether a normal user is allowed.
Output
Per slot: VERIFIED + the one line of what you observed · GAP + why it cannot be checked in this environment · FAILED + the exact output and the smallest reproduction. Never silently skip a slot. Do not fix anything — report, and let the build role fix it.
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 · 34 lines · 28 tokens per session scan A 9f153670289f
loop-verifier is an agent published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 398 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
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.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
test-engineer
Examines code and plans tests focused on observable behavior — inputs, outputs, and collaborator interactions — rather than internal code paths. Identifies untested behaviors, recommends test doubles (stubs for queries, mock expectations for commands) for isolation, and produces a prioritized test plan with…
evidence-based-investigator
Investigates codebase issues by gathering concrete evidence — file paths, line numbers, code snippets, error messages, git history, and test coverage. Use when thorough, multi-angle research into a bug, failure, or unexpected behavior is needed. Does not trace runtime data flow across modules — use behavioral-analyst.…