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/payrequest/claude-plugins/deployment-engineergit clone --depth 1 https://github.com/PayRequest/claude-pluginsWhat 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.00077 | $0.01708 |
| Opus 5 | $0.00039 | $0.00854 |
| Sonnet 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 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.
This is a copy
97% identical to deployment-engineer — 2 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.
- yesterday First seen · 141 lines · 77 tokens per session scan A 671a2fe7394e
deployment-engineer is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 10mo ago), licensed MIT. It adds 77 tokens to every session and 1,708 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to deployment-engineer, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.