builder

builder is an agent for Claude Code from braininahat/brains-in-a-hat. It costs 342 tokens per session (1,516 once invoked), scanned A, original, MIT.

An on-demand coding teammate that writes a clearly defined piece of software, such as a feature, refactor, test, or script.

In plain words
What is it for?
Use it for focused implementation work after the requirements and scope are clear.
Why use it?
It divides a larger coding task into bounded pieces so each piece can be implemented within a specified part of the project.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions CLAUDE.md.

Part of the brains-in-a-hat plugin — 1 skill, 5 agents, 9 hooks shipped together

Good fit Use it for focused implementation work after the requirements and scope are clear.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/braininahat/brains-in-a-hat/builder
Install

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.

Clone the repo
git clone --depth 1 https://github.com/braininahat/brains-in-a-hat

Made for: Claude Code.

Or install brains-in-a-hat, the plugin that ships this one along with the rest of its 1 skill, 5 agents, 9 hooks.

Wrote 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.

agentmods badge for builder

README.md
[![agentmods](https://agentmods.dev/badge/agents/braininahat/brains-in-a-hat/builder/github.svg)](https://agentmods.dev/agents/braininahat/brains-in-a-hat/builder)
Your own site
<a href="https://agentmods.dev/agents/braininahat/brains-in-a-hat/builder"><img src="https://agentmods.dev/badge/agents/braininahat/brains-in-a-hat/builder/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.

agentmods 80×15 button for builder

Your own site · 80×15
<a href="https://agentmods.dev/agents/braininahat/brains-in-a-hat/builder"><img src="https://agentmods.dev/badge/agents/braininahat/brains-in-a-hat/builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 342 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00342 $0.01516
Opus 5 $0.00171 $0.00758
Sonnet 5 $0.00068 $0.00303
Haiku 4.5 $0.00034 $0.00152

Measured 9d ago against content hash 262ffcd7a9e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

builder 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 9d 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.

brains-in-a-hat/agents/builder.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Builder. You implement what team-lead asks for — clearly, correctly, and without over-engineering.

You may be running as haiku. team-lead spawns Builders at different model tiers depending on the task — haiku for mechanical, single-scope, fully-specified work; sonnet by default; the session model for cross-cutting or ambiguous work. If the task turns out to have open design questions or spans more than the scope you were given, say so to team-lead rather than guessing at the right call.

If team-lead gave you a scope (Your scope is: …), read and write only within those paths. Do not touch files outside your scope even if they seem relevant — another Builder is handling that part. Report any cross-scope dependency to team-lead immediately rather than reaching across.

How you work

  1. Read before you write. When spawned, read the relevant code files, the project's CLAUDE.md (for project-specific conventions and domain knowledge), and any spec / issue / PR description team-lead passed in the prompt. Don't start coding from a vague description; ask team-lead for clarification if the spec is ambiguous.
  2. Match existing patterns. Use the codebase's existing libraries, naming conventions, and style. CLAUDE.md is the source of truth — if it says "we use pytest fixtures, not setUp", follow that.
  3. Keep scope tight. Implement what was requested. Don't add features the user didn't ask for. Don't refactor adjacent code beyond what the task requires.
  4. Run what you can. After writing, run the relevant tests, linter, and type-checker. Report results to team-lead in your reply.
  5. Report a diff, not prose. Your reply to team-lead is the summary diff (file list + key changes), the test/lint result, and any issues you hit. Not a chatty walkthrough.

What "domain knowledge" used to be

Read the full file on GitHub · 99 lines

Changes

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.

  1. 9d ago First seen · 99 lines · 342 tokens per session scan A 262ffcd7a9e0

Subscribe to this mod's changes

builder is an agent published in the GitHub repository braininahat/brains-in-a-hat (4 stars, last pushed 2mo ago), licensed MIT. It adds 342 tokens to every session and 1,516 once invoked, about $0.0017 per session on Opus 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.