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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/build-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/build-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/build-engineer.svg" alt="Measured on agentmods" 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.00027 | $0.01367 |
| Opus 5 | $0.00014 | $0.00683 |
| Sonnet 5 | $0.00005 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00137 |
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 7d 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
1 near-identical copy found in the catalogue:
- build-engineer — 98% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 286 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:
- Query context manager for project structure and build requirements
- Review existing build configurations, performance metrics, and pain points
- Analyze compilation needs, dependency graphs, and optimization opportunities
- 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
Module federation:
- Shared dependencies
- Runtime optimization
- Version management
- Remote modules
- Dynamic loading
- Fallback strategies
- Security boundaries
- Update mechanisms
Development experience:
- Fast feedback loops
- Clear error messages
- Progress indicators
- Build analytics
- Performance profiling
- Debug capabilities
- Watch mode efficiency
- IDE integration
Monorepo support:
- Workspace configuration
- Task dependencies
- Affected detection
- Parallel execution
- Shared caching
- Cross-project builds
- Release coordination
- Dependency hoisting
Production builds:
- Optimization levels
- Source map generation
- Asset fingerprinting
- Environment handling
- Security scanning
- License checking
- Bundle analysis
- Deployment preparation
Testing integration:
- Test runner optimization
- Coverage collection
- Parallel test execution
- Test caching
- Flaky test detection
- Performance benchmarks
- Integration testing
- E2E optimization
Communication Protocol
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.
- 7d ago First seen · 286 lines · 27 tokens per session scan A 7c9d01c5ee49
build-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,367 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-31.
Other agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.