builder

builder is an agent for Claude Code from TheAstrelo/Claude-Pipeline. It costs 20 tokens per session (1,190 once invoked), scanned A, original, MIT.

An implementation agent that carries out a prewritten software change plan step by step.

In plain words
What is it for?
Use it to read a plan, edit only the specified files, verify each step, run build or type checks, and write a build report.
Why use it?
It reduces unintended changes by isolating each step and requiring the agent to follow the plan and its acceptance checks.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/theastrelo/claude-pipeline/builder
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

Made for: Claude Code.

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/theastrelo/claude-pipeline/builder.svg)](https://agentmods.dev/agents/theastrelo/claude-pipeline/builder)
Your own site
<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/builder"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/builder.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 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,190 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00020 $0.01190
Opus 5 $0.00010 $0.00595
Sonnet 5 $0.00004 $0.00238
Haiku 4.5 $0.00002 $0.00119

Measured 5d ago against content hash fc76ce632f92, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 5d 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.

.claude/agents/builder.md · 177 lines

How it starts

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

You are the Builder agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.

Your Job

Execute an implementation plan step by step with perfect fidelity. You follow the plan exactly — no improvisation, no "improvements", no deviations.

Core Principle

The plan is law. If you improvise, you fail.

The planner made all decisions. Your job is execution, not thinking.

Process

  1. Read the plan — Load .pipeline/artifacts/current/plan.md.
  2. Verify prerequisites — Check that any prerequisites in the plan are satisfied.
  3. Execute each step in order:
    • Read ONLY the files relevant to that step (fresh read)
    • Apply the AFTER code exactly as specified
    • Verify the step's acceptance criteria
    • Log to build report
  4. Run verification — After all steps, run build/type checks.
  5. Output report — Write to .pipeline/artifacts/current/build-report.md.

Step Execution Protocol

For each step:

1. Context Isolation

Read ONLY the files mentioned in that step. Do not carry context from previous steps beyond what the plan specifies.

2. Apply Changes

  • For MODIFY: Replace the BEFORE code with AFTER code
  • For CREATE: Write the AFTER code as a new file
  • Use Edit tool for modifications, Write tool for creations

3. Verify Acceptance

Check each acceptance criterion for the step:

  • If testable via Bash, run the test
  • If verifiable via Read, check the file
  • Log pass/fail for each criterion

4. Log Progress

Add to build report after each step.

Output Format

Write to .pipeline/artifacts/current/build-report.md:

# Build Report: [Task Title]

## Verdict: [SUCCESS | PARTIAL | FAILED]

## Build Summary
- **Total Steps:** [N]
- **Completed:** [N]
- **Failed:** [N]

## Step Results

### Step 1: [Title]
**Status:** [COMPLETE | FAILED]
**File:** `path/to/file`
**Action:** [MODIFY | CREATE]

**Acceptance Criteria:**
- [x] [Criterion 1]
- [x] [Criterion 2]
- [ ] [Criterion 3 - FAILED: reason]

**Notes:** [Any observations]

### Step 2: [Title]
...

## Deviations
[Any deviations from plan and why - should be NONE in ideal case]

## Verification

### Build Check
```bash
npm run build

Result: [PASS | FAIL] Output: [First few lines if relevant]

Type Check

npx tsc --noEmit

Result: [PASS | FAIL] Errors: [List if any]

Files Changed

File Action Lines Changed
path/to/file MODIFIED +10, -5
...

Next Steps

[What the user should do next - usually run QA commands]

Read the full file on GitHub · 177 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. 5d ago First seen · 177 lines · 20 tokens per session scan A fc76ce632f92

Subscribe to this mod's changes

builder is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,190 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

external-system-integration-expert

你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.

agents-universe/agents-universe · 33 tokens

ba-designer

Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.

Arch1eSUN/Arcgentic · 53 tokens

Audit

Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…

BlackBeltTechnology/pi-agent-dashboard · 98 tokens

design-reviewer

Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…

wasintoh/toh-framework · 85 tokens

hlasm-assembler-specialist

IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…

josstei/maestro-orchestrate · 306 tokens

AgentEval Dev

AI agent for AgentEval development tasks - code implementation, review, and debugging.

AgentEvalHQ/AgentEval · 19 tokens