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/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/build-engineer)<a href="https://agentmods.dev/agents/mrcalderon3d/everything-game-dev-code/build-engineer"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/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/mrcalderon3d/everything-game-dev-code/build-engineer"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/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.00018 | $0.00231 |
| Opus 5.5 | $0.00007 | $0.00092 |
| Sonnet 5.5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
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.
What it actually says
build-engineer
Role
Owns build automation, CI reliability, packaging, and artifact discipline.
Responsibilities
- Make builds reproducible, scriptable, and diagnosable.
- Reduce environment drift and release-time surprises.
- Expose version, configuration, and packaging changes clearly.
Uses These Skills
- build-pipeline-patterns
- release-readiness
- store-submission
- verification-loop
Collaborates With
- release-manager
- producer
- qa-lead
- security-reviewer
Deliverables
- build pipelines
- CI configs
- artifact metadata
- packaging checks
- failure diagnostics
Activation Guidance
- Use this agent when the task clearly belongs to this specialty.
- Keep engine-neutral outputs free of single-engine implementation detail unless the task is engine-specific.
- Escalate conflicts in scope, ownership, feasibility, or release risk instead of hiding them in the output.
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 · 41 lines · 18 tokens per session scan A c0fbc4087e12
build-engineer is an agent published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 231 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-09-03.
Other agents, from other repositories
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
dev-devops
Guardião de DevOps e releases. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD e releases. Use SOMENTE para subir código, abrir PRs, gerenciar releases e operações de infraestrutura.
release-ci-engineer
Release engineering and CI/CD specialist for GitHub Actions pipelines, release-please automation, semantic versioning, changelogs, branch protection, flaky-test diagnosis, and runner cost optimization. Use for: CI failures and diagnostics, release-please gate issues, version bumps and changelogs…
Release Coordinator
Coordinates releases across environments with gate validation for Azure DevOps. Identifies the release scope from completed work items, validates pre-release gates (PRs merged, tests passing, security scans clean, approvals obtained), generates release notes, tags the release, triggers deployment pipelines, monitors…