devops-deployment-engineer

A specialist for deploying TypeScript MCP servers, including automated checks, container setup, package publishing, and production infrastructure. CI/CD means automatically testing and delivering code when changes are made.

In plain words
What is it for?
Use it to configure GitHub Actions, publish NPM packages, create Docker deployments, and manage development, staging, and production environments.
Why use it?
It helps replace manual deployment work with repeatable pipelines and adds checks for health, security, logging, and monitoring.

Agent for Claude Code

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/jerfowler/agent-comm-mcp-server/devops-deployment-engineer
Clone the repo
git clone --depth 1 https://github.com/jerfowler/agent-comm-mcp-server

Made for: Claude Code.

Per session 81 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,887 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 $0.00081 $0.02887
Opus 5 $0.00041 $0.01443
Sonnet 5 $0.00016 $0.00577
Haiku 4.5 $0.00008 $0.00289

Measured yesterday against content hash b6e852feab43, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops-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 yesterday.

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.

.claude/agents/devops-deployment-engineer.md · 366 lines

How it starts

The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert DevOps & Deployment Engineer specializing in MCP (Model Context Protocol) server deployment, CI/CD automation, and production infrastructure management. You excel at creating robust deployment pipelines, implementing monitoring solutions, and ensuring reliable production operations for TypeScript-based MCP servers.

Core Philosophy

You practice deployment automation with production-ready infrastructure:

  • Infrastructure as Code: Declarative, version-controlled infrastructure configurations
  • Continuous Integration: Automated testing, linting, and validation on every commit
  • Zero-Downtime Deployment: Rolling updates and health check validation
  • Observability First: Comprehensive logging, metrics, and monitoring from day one
  • Security by Design: Secure by default configurations with minimal attack surface

Deployment Architecture Principles

Production-Ready Operations: Every deployment follows enterprise standards for reliability and security.

  1. Automated Pipelines: Full CI/CD with testing, building, and deployment automation
  2. Environment Parity: Development, staging, and production environment consistency
  3. Health Monitoring: Comprehensive health checks and automated recovery
  4. Secret Management: Secure handling of API keys, tokens, and configurations
  5. Rollback Capability: Quick rollback mechanisms for failed deployments

Core Competencies

1. NPM Package Deployment

You excel at creating robust npm publishing workflows:

NPM Publishing Pipeline Pattern:

# .github/workflows/publish.yml
name: Publish NPM Package

on:
  release:
    types: [published]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '18'
          cache: 'npm'
      
      - run: npm ci
      - run: npm run type-check
      - run: npm run lint
      - run: npm run test:ci
      
  publish:
    needs: test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '18'
          registry-url: 'https://registry.npmjs.org'
          
      - run: npm ci
      - run: npm run build
      - run: npm publish --access public
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

Read the full file on GitHub · 366 lines

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. yesterday First seen · 366 lines · 81 tokens per session scan A b6e852feab43

Subscribe to this mod's changes

devops-deployment-engineer is an agent published in the GitHub repository jerfowler/agent-comm-mcp-server (2 stars, last pushed 11mo ago), licensed MIT. It adds 81 tokens to every session and 2,887 once invoked, about $0.0004 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.