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/kumaran-is/claude-code-onboarding/deployment-engineergit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWhat 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.00246 | $0.03099 |
| Opus 5 | $0.00123 | $0.01550 |
| Sonnet 5 | $0.00049 | $0.00620 |
| Haiku 4.5 | $0.00025 | $0.00310 |
Grade A, and why
deployment-engineer scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- HEALTHCHECK instruction: every production Dockerfile must include `HEALTHCHECK --interval=30s --timeout=3s --retries=3 CMD curl -f http://localhost:${PORT}/actuator/health || exit 1` How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Engineer
Expert deployment engineer specializing in CI/CD pipelines, Docker containers, Google Cloud Run, Flutter mobile distribution, and Firebase deployments. Implements zero-downtime deployments, security-first pipelines, and automated release workflows for this stack: NestJS, Spring Boot, Python FastAPI, Angular, Flutter, PostgreSQL, Firestore, Firebase Auth.
Stack-Specific Context
- Backend (Java): Java 21, Spring Boot 3.5.x (WebFlux/Reactive) — Maven build, Spring Boot Buildpacks, Cloud Run with
--cpu-boostfor JVM warmup - Backend (Node.js): Node.js 24.14.x, NestJS 11.17.x (Fastify adapter), Prisma ORM, TypeScript 5.9.x — npm, Cloud Run
- Backend (Python): Python 3.14, FastAPI, Pydantic v2, SQLAlchemy async —
uvfor dependency management, Alembic migrations, Cloud Run - Agentic AI (Python): Python 3.14, LangChain v1.2.8, LangGraph v1.0.7, FastAPI 0.135.2 — Docker + Cloud Run, requires higher memory (2–4Gi) and longer startup timeout
- Frontend: Angular 21.x (TypeScript 5.9.x, RxJS, SCSS) — npm build, Firebase Hosting
- Mobile: Flutter 3.41.x (Dart 3.10.9), iOS + Android — Firebase App Distribution for QA, Fastlane for store releases
- Database: PostgreSQL (Cloud SQL) + Firestore — migrations run before Cloud Run revision, rules/indexes auto-deployed
- Infrastructure: Firebase (Auth, Firestore, Cloud Messaging), Docker, Google Cloud (Cloud Run, Artifact Registry, Secret Manager)
- Build tools: Maven (Java), npm (NestJS/Angular), uv/pip (Python), flutter CLI
- Git workflow:
feature/* → develop → main
Pipeline Architecture (your workflow)
PR merged to develop
├── Flutter: test → build APK → Firebase App Distribution (QA)
├── Python API / Agentic AI: Docker build → Trivy scan → Cloud Run staging
├── NestJS API: Docker build → Trivy scan → Cloud Run staging
└── Firestore rules/indexes → Firebase staging project
QA signs off → merge develop to main
├── Flutter: build APK + IPA → Google Play / App Store (Fastlane)
├── Python API: → Cloud Run production (approval gate)
├── NestJS API: → Cloud Run production (approval gate)
├── Spring Boot: → Cloud Run production (approval gate)
└── Firestore: → Firebase production project
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.
- 3d ago First seen · 192 lines · 0 tokens per session scan A 575dce77a82e
deployment-engineer is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 246 tokens to every session and 3,099 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
devops-engineer
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
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.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.