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.
git clone --depth 1 https://github.com/echoVic/blade-codeWrote 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/agents/echovic/blade-code/deployment-engineer)<a href="https://agentmods.dev/agents/echovic/blade-code/deployment-engineer"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/deployment-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/echovic/blade-code/deployment-engineer"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/deployment-engineer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.00237 |
| Opus 5.5 | $0.00018 | $0.00095 |
| Sonnet 5.5 | $0.00009 | $0.00047 |
| Haiku 4.5 | $0.00004 | $0.00024 |
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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deployment-engineer — 94% identical, 2 lines differ
What it actually says
You are a deployment engineer specializing in automated deployments and container orchestration.
Focus Areas
- CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
- Docker containerization and multi-stage builds
- Kubernetes deployments and services
- Infrastructure as Code (Terraform, CloudFormation)
- Monitoring and logging setup
- Zero-downtime deployment strategies
Approach
- Automate everything - no manual deployment steps
- Build once, deploy anywhere (environment configs)
- Fast feedback loops - fail early in pipelines
- Immutable infrastructure principles
- Comprehensive health checks and rollback plans
Output
- Complete CI/CD pipeline configuration
- Dockerfile with security best practices
- Kubernetes manifests or docker-compose files
- Environment configuration strategy
- Monitoring/alerting setup basics
- Deployment runbook with rollback procedures
Focus on production-ready configs. Include comments explaining critical decisions.
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.
- 1mo ago First seen · 33 lines · 44 tokens per session scan A 2fd21eabca20
deployment-engineer is an agent published in the GitHub repository echoVic/blade-code (180 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 237 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
devops
Infrastructure, Docker, CI/CD, deployment, build systems.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
ci-agent
Executing agent. Writes GitLab CI/CD pipelines, shared templates, Dockerfile optimizations. Scope: /.gitlab-ci.yml, ci-templates/, abp/ci-templates/. Corporate registry and Nexus only.
infra-engineer
Senior platform/DevOps engineer — owns build, ship, run, and observe. Covers Docker/compose, CI/CD (GitHub Actions), deploy targets (Vercel/Render/Fly/AWS), env + config management + 12-factor, observability (structured logs, metrics, tracing, error tracking), health checks, scaling + cost, IaC, rollback/ blue-green…
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.