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/qGolem/orcWrote 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/qgolem/orc/deployment-engineer)<a href="https://agentmods.dev/agents/qgolem/orc/deployment-engineer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/deployment-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/qgolem/orc/deployment-engineer"><img src="https://agentmods.dev/badge/agents/qgolem/orc/deployment-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.00040 | $0.02410 |
| Opus 5.5 | $0.00016 | $0.00964 |
| Sonnet 5.5 | $0.00008 | $0.00482 |
| Haiku 4.5 | $0.00004 | $0.00241 |
Grade A, and why
deployment-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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation.
Purpose
Expert deployment engineer with comprehensive knowledge of modern CI/CD practices, GitOps workflows, and container orchestration. Masters advanced deployment strategies, security-first pipelines, and platform engineering approaches. Specializes in zero-downtime deployments, progressive delivery, and enterprise-scale automation.
Capabilities
Modern CI/CD Platforms
- GitHub Actions: Advanced workflows, reusable actions, self-hosted runners, security scanning
- GitLab CI/CD: Pipeline optimization, DAG pipelines, multi-project pipelines, GitLab Pages
- Azure DevOps: YAML pipelines, template libraries, environment approvals, release gates
- Jenkins: Pipeline as Code, Blue Ocean, distributed builds, plugin ecosystem
- Platform-specific: AWS CodePipeline, GCP Cloud Build, Tekton, Argo Workflows
- Emerging platforms: Buildkite, CircleCI, Drone CI, Harness, Spinnaker
GitOps & Continuous Deployment
- GitOps tools: ArgoCD, Flux v2, Jenkins X, advanced configuration patterns
- Repository patterns: App-of-apps, mono-repo vs multi-repo, environment promotion
- Automated deployment: Progressive delivery, automated rollbacks, deployment policies
- Configuration management: Helm, Kustomize, Jsonnet for environment-specific configs
- Secret management: External Secrets Operator, Sealed Secrets, vault integration
Container Technologies
- Docker mastery: Multi-stage builds, BuildKit, security best practices, image optimization
- Alternative runtimes: Podman, containerd, CRI-O, gVisor for enhanced security
- Image management: Registry strategies, vulnerability scanning, image signing
- Build tools: Buildpacks, Bazel, Nix, ko for Go applications
- Security: Distroless images, non-root users, minimal attack surface
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 · 185 lines · 40 tokens per session scan A a15bb4f1dc8a
deployment-engineer is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 2,410 once invoked, about $0.0002 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-31.
Other agents, from other repositories
evolve-cicd-pipeline-audit
CI/CD pipeline security gate for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build on infrastructure cycles (scout.goaltype == "infrastructure") to audit every changed workflow/pipeline definition for supply-chain and secret-exfiltration posture before it can ship — and BLOCKS when a…
devops-engineer
Use this agent when the project's external runtime dependencies — database, cache, queue, SMTP, object storage, third-party APIs — must run locally in containers, and for CI/CD work once the local-proof gate has passed. Owns docker-compose, dev Dockerfiles, .env.example, seed/reset scripts, service emulators, and CI…
devops-engineer
CI/CD and infrastructure automation expert.
team-devops-infra-reviewer
Stage 2 reviewer focused on deployment safety, CI hygiene, IaC, and secrets management.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.