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/HermeticOrmus/LibreUIUX-Claude-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/hermeticormus/libreuiux-claude-code/deployment-engineer)<a href="https://agentmods.dev/agents/hermeticormus/libreuiux-claude-code/deployment-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreuiux-claude-code/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/hermeticormus/libreuiux-claude-code/deployment-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreuiux-claude-code/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.00077 | $0.01708 |
| Opus 5.5 | $0.00031 | $0.00683 |
| Sonnet 5.5 | $0.00015 | $0.00342 |
| Haiku 4.5 | $0.00008 | $0.00171 |
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.
This is a copy
89% identical to cicd-automation-deployment-engineer — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 141 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
Kubernetes Deployment Patterns
- Deployment strategies: Rolling updates, blue/green, canary, A/B testing
- Progressive delivery: Argo Rollouts, Flagger, feature flags integration
- Resource management: Resource requests/limits, QoS classes, priority classes
- Configuration: ConfigMaps, Secrets, environment-specific overlays
- Service mesh: Istio, Linkerd traffic management for deployments
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 · 141 lines · 77 tokens per session scan A 672df91a83da
deployment-engineer is an agent published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 15d ago), licensed MIT. It adds 77 tokens to every session and 1,708 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to cicd-automation-deployment-engineer, differing in 24 lines, and is treated as a copy.
Other agents, from other repositories
devops-engineer
Build pipelines, CI/CD configuration, version control workflow, branching strategy, automated test pipelines, deployment infrastructure.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
Automatyzuje droge od commita do produkcji
Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się…
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.
sites-devops
Guardião de DevOps e releases para sites. Autoridade EXCLUSIVA para git push, gh pr create/merge, CI/CD, deploys em Vercel/Netlify e releases.
creo-github-cli
GitHub CLI expert for PRs, issues, Actions workflows, secrets, releases, and repository management.