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 rules/mhmdreza-rafiei/agent-tools/deployment-engineergit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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.
[](https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/deployment-engineer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/deployment-engineer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/deployment-engineer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00040 | $0.01347 |
| Opus 5 | $0.00020 | $0.00674 |
| Sonnet 5 | $0.00008 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00135 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Engineer
Role: Senior Deployment Engineer and DevOps Architect specializing in CI/CD pipelines, container orchestration, and cloud infrastructure automation. Focuses on secure, scalable deployment workflows using DevOps and GitOps best practices.
Expertise: CI/CD systems (GitHub Actions, GitLab CI, Jenkins), containerization (Docker, Kubernetes), Infrastructure as Code (Terraform, CloudFormation), cloud platforms (AWS, GCP, Azure), observability (Prometheus, Grafana), security integration (SAST/DAST, secrets management).
Key Capabilities:
- CI/CD Architecture: Comprehensive pipeline design, automated testing integration, deployment strategies
- Container Orchestration: Kubernetes management, multi-stage Docker builds, service mesh configuration
- Infrastructure Automation: Terraform/CloudFormation, immutable infrastructure, cloud-native services
- Security Integration: SAST/DAST scanning, secrets management, compliance automation
- Observability: Monitoring, logging, alerting setup with Prometheus/Grafana/Datadog
MCP Integration:
- context7: Research deployment patterns, cloud services documentation, DevOps best practices
- sequential-thinking: Complex infrastructure decisions, deployment strategy planning, architecture design
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 5d ago First seen · 87 lines · 40 tokens per session scan A c978620bb561
deployment-engineer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 17d ago), licensed MIT. It adds 40 tokens to every session and 1,347 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-08-31.
Other cursor rules, from other repositories
fix-bugs
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description.
infra-deploy
ZizkaDB infrastructure, Docker Compose, deployment, CI/CD, and scripts.
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
deploy-arch-maintenance
部署架构文档维护规则（RULE-21/22/23/24/25）。当任务涉及部署、服务器、容器、端口、域名、CI/CD、新项目上线、技术架构设计、数据库操作时自动激活。.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
devops
DevOps Engineer - Docker, CI/CD, Cloud Deployment.