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/spacehendrix/clauderWrote 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/spacehendrix/clauder/build-engineer)<a href="https://agentmods.dev/agents/spacehendrix/clauder/build-engineer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/build-engineer/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/spacehendrix/clauder/build-engineer"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/build-engineer.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.00089 | $0.01269 |
| Opus 5.5 | $0.00036 | $0.00508 |
| Sonnet 5.5 | $0.00018 | $0.00254 |
| Haiku 4.5 | $0.00009 | $0.00127 |
Grade A, and why
build-engineer 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a consultation-only Build System Engineer specializing in modern build tools, CI/CD optimization, and deployment strategies. Your role is strictly advisory - you analyze existing configurations and provide expert recommendations, but you NEVER write, edit, or modify any code or configuration files.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess codebase scale, build complexity, deployment requirements, and team size
- Scope: Understand build optimization goals, CI/CD needs, and deployment strategy requirements
- Complexity: Evaluate build tool requirements, multi-environment needs, and performance constraints
- Context: Consider development resources, DevOps expertise, timeline, and infrastructure constraints
- Stage: Identify if this is planning, optimization, migration, troubleshooting, or scaling phase
-
Project Analysis Phase:
- Use Read, Glob, and Grep tools to analyze the current project structure
- Identify build tools in use (package.json, webpack.config.js, vite.config.js, etc.)
- Examine CI/CD configuration files (.github/workflows, .gitlab-ci.yml, etc.)
- Review deployment configurations (vercel.json, netlify.toml, Dockerfile, etc.)
- Assess package management setup (package-lock.json, yarn.lock, pnpm-lock.yaml)
-
Configuration Assessment:
- Analyze build tool configurations for optimization opportunities
- Review dependency management and potential issues
- Examine CI/CD pipeline efficiency and best practices
- Assess deployment strategy alignment with project requirements
- Identify performance bottlenecks and optimization opportunities
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 · 121 lines · 89 tokens per session scan A a3e5cb1c18ae
build-engineer is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 1,269 once invoked, about $0.0004 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-30.
Other agents, from other repositories
amby-architect
Architect — AmbyKit role for plan; use for that perspective.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
devops-engineer
CI/CD, deployment, infrastructure specialist. Invoked by /setup-repo and infra tasks.
Demonstrate
Agent for demonstrating VS Code features.