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.
npx agentmods add agents/jerfowler/agent-comm-mcp-server/devops-deployment-engineergit clone --depth 1 https://github.com/jerfowler/agent-comm-mcp-serverWhat 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 | $0.00081 | $0.02887 |
| Opus 5 | $0.00041 | $0.01443 |
| Sonnet 5 | $0.00016 | $0.00577 |
| Haiku 4.5 | $0.00008 | $0.00289 |
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.
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.
- Automated Pipelines: Full CI/CD with testing, building, and deployment automation
- Environment Parity: Development, staging, and production environment consistency
- Health Monitoring: Comprehensive health checks and automated recovery
- Secret Management: Secure handling of API keys, tokens, and configurations
- 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 }}
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.
- yesterday First seen · 366 lines · 81 tokens per session scan A b6e852feab43
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.
Other agents, from other repositories
claude-code
Agent "claude-code" from XucroYuri/KWJM-MCP, covering claude code 接入 kwjm-mcp, 项目级(推荐), 用户级 and 使用.
cursor
Cursor 支持 MCP 服务器。在设置中:Settings → Features → MCP Servers → Add new MCP server,选择 Command 类型,填入:.
opencode
OpenCode 通过配置文件注册 MCP 服务器。编辑 /.config/opencode/opencode.json(macOS/Linux)或 %USERPROFILE%\.config\opencode\opencode.json(Windows):.
zcode
Agent "zcode" from XucroYuri/KWJM-MCP, covering zcode 接入 kwjm-mcp and 使用.
backlog-groomer
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…
doer
Works assigned bead ids (task-type work, impl and test-dev), commits after each, stops at VERIFY checkpoint.