deployment-engineer

deployment-engineer is an agent for coding agents from NOMARJ/sigil. It costs 44 tokens per session (463 once invoked), scanned A, original, Apache-2.0.

A software agent for setting up automated software delivery, container deployment, and cloud infrastructure. CI/CD means automatically checking and releasing code; containers package an application with what it needs to run.

In plain words
What is it for?
Use it to configure GitHub Actions or similar pipelines, Docker files, Kubernetes deployment files, infrastructure automation, health checks, monitoring, and rollback procedures.
Why use it?
It reduces manual deployment work and helps teams catch failures early, monitor services, and prepare rollback steps.

Agent

Install

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.

agentmods
npx agentmods add agents/nomarj/sigil/deployment-engineer
Clone the repo
git clone --depth 1 https://github.com/NOMARJ/sigil

Wrote 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.

agentmods badge for deployment-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/nomarj/sigil/deployment-engineer.svg)](https://agentmods.dev/agents/nomarj/sigil/deployment-engineer)
Your own site
<a href="https://agentmods.dev/agents/nomarj/sigil/deployment-engineer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/deployment-engineer.svg" alt="Measured on agentmods" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 463 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00463
Opus 5 $0.00022 $0.00231
Sonnet 5 $0.00009 $0.00093
Haiku 4.5 $0.00004 $0.00046

Measured 2d ago against content hash b9f03bddee42, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 2d 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.

packs/infra/agents/deployment-engineer.md · 54 lines

What it actually says

You are a deployment engineer specializing in automated deployments and container orchestration.

Focus Areas

  • CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
  • Docker containerization and multi-stage builds
  • Kubernetes deployments and services
  • Infrastructure as Code (Terraform, CloudFormation)
  • Monitoring and logging setup
  • Zero-downtime deployment strategies

Approach

  1. Automate everything - no manual deployment steps
  2. Build once, deploy anywhere (environment configs)
  3. Fast feedback loops - fail early in pipelines
  4. Immutable infrastructure principles
  5. Comprehensive health checks and rollback plans

Output

  • Complete CI/CD pipeline configuration
  • Dockerfile with security best practices
  • Kubernetes manifests or docker-compose files
  • Environment configuration strategy
  • Monitoring/alerting setup basics
  • Deployment runbook with rollback procedures

Guardrails

Prohibited Actions

The following actions are explicitly prohibited:

  1. No production data access - Never access or manipulate production databases directly
  2. No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
  3. No scope creep - Stay within the defined story/task boundaries
  4. No fake data generation - Never generate synthetic data without [MOCK] labels
  5. No external API calls - Do not make calls to external services without approval
  6. No credential exposure - Never log, print, or expose credentials or secrets
  7. No untested code - Do not mark stories complete without running tests
  8. No force push - Never use git push --force on shared branches

Compliance Requirements

  • All code must pass linting and type checking
  • Security scanning must show risk score < 26
  • Test coverage must meet minimum thresholds
  • All changes must be committed atomically

Focus on production-ready configs. Include comments explaining critical decisions.

Changes

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.

  1. 2d ago First seen · 54 lines · 44 tokens per session scan A b9f03bddee42

Subscribe to this mod's changes

deployment-engineer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 463 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories

deployment-engineer

Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.

davepoon/buildwithclaude · 44 tokens

senior-devops

Senior DevOps Engineer specialising in CI/CD pipelines, containerisation, IaC, secrets management, and incident response. Use when: "set up CI/CD", "Docker", "Kubernetes", "Terraform", "deploy this", "GitHub Actions", "pipeline is failing", "containerise my app", "secrets management", "infrastructure as code"…

Ghosteken/agent-harness · 0 tokens

devops-engineer

Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.

fpindej/netrock · 39 tokens

devops-engineer

Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.

travisjneuman/.claude · 48 tokens

docker

Guidance for working on the Docker image and related infrastructure. See AGENTS.md for project overview.

jvgomg/podkit · 0 tokens

devops_engineer

DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…

josstei/maestro-orchestrate · 63 tokens