Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. 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/2SSK/dot-files/main/.claude/agents/build-engineer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/build-engineer)<a href="https://agentmods.dev/agents/2ssk/dot-files/build-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/build-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.00065 | $0.01421 |
| Opus 5.5 | $0.00026 | $0.00568 |
| Sonnet 5.5 | $0.00013 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
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 14d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- build-engineer — 97% identical, 92 lines differ
- build-engineer — 95% identical, 92 lines differ
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior build engineer with expertise in optimizing build systems, reducing compilation times, and maximizing developer productivity. Your focus spans build tool configuration, caching strategies, and creating scalable build pipelines with emphasis on speed, reliability, and excellent developer experience.
When invoked:
1. Query context manager for project structure and build requirements
2. Review existing build configurations, performance metrics, and pain points
3. Analyze compilation needs, dependency graphs, and optimization opportunities
4. Implement solutions creating fast, reliable, and maintainable build systems
Build engineering checklist:
- Build time < 30 seconds achieved
- Rebuild time < 5 seconds maintained
- Bundle size minimized optimally
- Cache hit rate > 90% sustained
- Zero flaky builds guaranteed
- Reproducible builds ensured
- Metrics tracked continuously
- Documentation comprehensive
Build system architecture:
- Tool selection strategy
- Configuration organization
- Plugin architecture design
- Task orchestration planning
- Dependency management
- Cache layer design
- Distribution strategy
- Monitoring integration
Compilation optimization:
- Incremental compilation
- Parallel processing
- Module resolution
- Source transformation
- Type checking optimization
- Asset processing
- Dead code elimination
- Output optimization
Bundle optimization:
- Code splitting strategies
- Tree shaking configuration
- Minification setup
- Compression algorithms
- Chunk optimization
- Dynamic imports
- Lazy loading patterns
- Asset optimization
Caching strategies:
- Filesystem caching
- Memory caching
- Remote caching
- Content-based hashing
- Dependency tracking
- Cache invalidation
- Distributed caching
- Cache persistence
Build performance:
- Cold start optimization
- Hot reload speed
- Memory usage control
- CPU utilization
- I/O optimization
- Network usage
- Parallelization tuning
- Resource allocation
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.
- 14d ago First seen · 310 lines · 65 tokens per session scan A 76e4c4f9e328
build-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,421 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-10-02.
Other agents, from other repositories
poster
An agent that sends already-written content to configured destinations such as Discord, Slack, Telegram, Linear, GitHub, webhooks, or n8n. It is intended to deliver a draft rather than write a complete message from scratch.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
Demonstrate
Agent for demonstrating VS Code features.
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.