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 skills add cbdreamer11/CB-loop-kit-claude-plugin --skill loop-councilgit 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/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-council)<a href="https://agentmods.dev/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-council"><img src="https://agentmods.dev/badge/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-council/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/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-council"><img src="https://agentmods.dev/badge/skills/cbdreamer11/cb-loop-kit-claude-plugin/loop-council.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.00052 | $0.00525 |
| Opus 5.5 | $0.00021 | $0.00210 |
| Sonnet 5.5 | $0.00010 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
loop-council 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council
A council exists so that a decision is made against reality instead of against recollection. It runs before the code, not as a review afterwards.
When it is required (not optional)
Look at what the change will touch — not at how confident you feel, because self-reported confidence is exactly the thing that fails:
- money, pricing, refunds, anything that charges someone
- permissions, authentication, or who can see whose data
- database schema, migrations, or anything that is hard to undo
- a public contract other code depends on
Two voices minimum. Three when it touches money, permissions, or schema.
The voices
Dispatch them in one message so they run in parallel, each blind to the others:
loop-planner— the architecture: the shape, the alternatives, what breaks later.loop-domain— the facts: decides against real documentation and the real installed behaviour, with URLs or exact strings. Never from memory.loop-auditor— the red team: its only job is to refute the proposed design before it exists. Give it the proposal, and tell it to assume there is a hole.
Resolving it
- Have each voice write its verdict to
.loop/council/<topic>-<voice>.mdas it finishes. Councils get interrupted; a verdict only in context is a verdict lost, and you should be able to resume without re-running the ones that finished. - If the red team and the architect disagree, the red team wins by default — or it escalates to the owner if it is really a business call. Never split the difference into something neither voice endorsed.
- Write the outcome into
.loop/DECISIONS.md: the decision, the alternative that was rejected and why, and the evidence. The rejected alternative is the part future sessions will need most.
What a council is not
It is not a vote to feel better about a decision already made, and it is not a substitute for reading the code. If the question can be answered by opening a file, open the file.
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 · 51 lines · 52 tokens per session scan A 71339b4483ff
loop-council is a skill published in the GitHub repository cbdreamer11/CB-loop-kit-claude-plugin (8 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 525 once invoked, about $0.0002 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 skills, from other repositories
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
senior-engineer
Use when reviewing code for architecture, quality, or correctness; making technical design decisions; evaluating trade-offs between approaches; refactoring complex systems; mentoring on engineering practices; writing technical design documents; or any task requiring deep technical judgement across the full stack.
kotlin-reviewer
Use when reviewing a Kotlin/Spring Boot pull request, systematic checklist covering architecture, idioms, testing, security, and observability.
frontend-reviewer
Use when reviewing a frontend pull request or diff, auditing a frontend repo for gaps, or checking whether code has drifted from the project's documented conventions.
review-board
Generate a single-file HTML "story-paced" walkthrough of a finished feature for human code review. Use after completing a feature or merging a PR — produces docs/review/ .html with sidebar nav, Why/Tradeoff/Deferred callouts, status pills, and a reviewer's checklist.
agentmaster-review
Adversarial code review with the agentmaster evidence pipeline. Use when the user asks for an agentmaster review of a diff, branch, or change set, or invokes /agentmaster-review. Assumes the code is guilty until proven working across correctness, structure, testability, flexibility, and security axes, with severity…