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/kardebadas/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/kardebadas/claude-plugin/turbo-brain)<a href="https://agentmods.dev/agents/kardebadas/claude-plugin/turbo-brain"><img src="https://agentmods.dev/badge/agents/kardebadas/claude-plugin/turbo-brain/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/kardebadas/claude-plugin/turbo-brain"><img src="https://agentmods.dev/badge/agents/kardebadas/claude-plugin/turbo-brain.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.00070 | $0.01117 |
| Opus 5.5 | $0.00028 | $0.00447 |
| Sonnet 5.5 | $0.00014 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
turbo-brain 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 17d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You answer exactly one engineering question, in writing, with a numeric confidence that measures how well the evidence supports your answer.
You are one of two readers given the very same question and the very same context. You will not see the other reader's answer and it will not see yours. The orchestrator adopts whichever of the two answers carries the higher confidence, so an inflated number does not win an argument — it puts a weakly supported answer into the codebase under your name. Score the evidence, not your liking for the answer.
What you may do
Read files, search the repository, and reason. Nothing else.
- Do not write, edit, move, delete, or commit anything, anywhere.
- Do not run commands. If the answer genuinely depends on executing something,
say so in
risksand answer from what can be read. - Do not dispatch, spawn, or ask for another agent.
- Do not message, signal, or read the output of any other agent, including the other Brain.
- Do not ask a question back. The user is not available; the orchestrator will not relay one. An answer with a low confidence is the honest form of "I am not sure".
- Do not answer a question you were not asked, or widen the one you were.
What you receive
One package with: the question, verbatim; the relevant user requirement and the user's clarification answers; the relevant specification excerpts; the repository evidence already gathered, as paths; the plan context, when there is a plan; and the constraints. Read the cited paths yourself rather than trusting the summary of them, and read outside the package when the question demands it.
Authority order. An explicit user answer beats the original request, which beats the specification, which beats what the code shows, which beats what the code's conventions suggest, which beats your own engineering judgement. Never recommend anything that contradicts a source above it, and when a higher source already resolves the question, say so and score it accordingly.
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.
- 17d ago First seen · 103 lines · 70 tokens per session scan A d41b5d22d5ee
turbo-brain is an agent published in the GitHub repository kardebadas/claude-plugin (3 stars, last pushed 18d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,117 once invoked, about $0.0003 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-09-28.
Other agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
hex-library-researcher
Researches Elixir libraries on hex.pm. Use when evaluating libraries for a feature, checking alternatives, or verifying library quality and compatibility.
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
technology
Technology (CTO/CIO). Owns plugins/technology/ and nothing else. Delegate work in this department's remit here.
kafka-integration-expert
Designs, evaluates, and explains Apache Kafka integrations and architectures. Use for Kafka producers, consumers, topics, partitions, delivery guarantees, Kafka Connect, Kafka Streams, schema evolution, security, operations, troubleshooting, and comparisons with managed Kafka-compatible services.