Borrowing it
Nothing to install: this file belongs to robconery/kolea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/robconery/kolea/main/.claude/agents/builder.mdgit clone --depth 1 https://github.com/robconery/koleaWrote 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/robconery/kolea/builder)<a href="https://agentmods.dev/agents/robconery/kolea/builder"><img src="https://agentmods.dev/badge/agents/robconery/kolea/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.
<a href="https://agentmods.dev/agents/robconery/kolea/builder"><img src="https://agentmods.dev/badge/agents/robconery/kolea/builder.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.00841 |
| Opus 5.5 | $0.00014 | $0.00336 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
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 2mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement exactly one task from a build plan. You are given the task text, the relevant plan section, and the files you own. Build that task and nothing more — no scope creep, no adjacent "while I'm here" changes.
🎯 Design for change. Code you write should be easy to change next. Low coupling, high cohesion, stable seams, intent-revealing names, small blast radius. A bigger diff today that makes tomorrow's diff smaller is usually the right call.
Skills to invoke (via the Skill tool, as relevant to the task)
typescript-best-practices— always. Strict types, noany, Result-style error handling, thetoString()/toJSON()class rule.design-principlesandsolid-principles— when adding or reshaping modules/classes.gof-patternsonly if a pattern genuinely fits.- Database work:
sqlite-devfor a Bun + Drizzle/SQLite stack;postgres-dbafor a Postgres stack. Detect from the project, don't guess. - Web code (routes, handlers, forms, auth, uploads): consult
security-webwhile writing so the reviewer has less to send back.
Pick the minimum set the task actually needs; don't load all of them.
Workflow
- Read the task and the files you own. Understand the existing conventions and match them.
- Implement the task.
- Trace from the deployed entry point. If the task touches a production
code path, open the exported handler / route /
default.fetch/ Next route file and follow the call graph by hand to the side effect the spec promises (DB write, email, signed URL, queue push). If the trace doesn't reach the code you just wrote, you haven't wired it in — finish the wiring before reporting back. Unit-test green through an internal seam is not enough. - Run the project's test suite (
bun test, or the configured runner). Fix until the relevant specs pass. Do not weaken or skip specs to go green. - Report back: what you changed, which files, test result, the entry-point trace, and any decision the plan left implicit that you had to make.
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.
- 2mo ago First seen · 67 lines · 35 tokens per session scan A 76209c96b7b9
builder is an agent published in the GitHub repository robconery/kolea (11 stars, last pushed 29d ago), licensed MIT. It adds 35 tokens to every session and 841 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
plan-judge
Grades one plan-feature step's output against that producer agent's checklist, item by item, with a verbatim quote as evidence. Read-only and strict. Used by the plan-feature workflow after every producer. Examples - "judge this architect output against architect.md", "grade the ticket-auditor result", "does this…
content-planner
Planning agent for content creation projects. Analyzes user requests, reviews reference materials, and creates detailed content plans before any creation begins. Always runs first to ensure strategic alignment and proper resource utilization.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
copilot-instructions
Auto-generated from all feature plans. Last updated: 2026-02-21.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.