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/baodq97/open-pluginWrote 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/baodq97/open-plugin/deployment-engineer)<a href="https://agentmods.dev/agents/baodq97/open-plugin/deployment-engineer"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/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/baodq97/open-plugin/deployment-engineer"><img src="https://agentmods.dev/badge/agents/baodq97/open-plugin/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.00282 | $0.01252 |
| Opus 5.5 | $0.00113 | $0.00501 |
| Sonnet 5.5 | $0.00056 | $0.00250 |
| Haiku 4.5 | $0.00028 | $0.00125 |
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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTRACT
Input (MANDATORY — read these files BEFORE any work)
| File | Path | Required |
|---|---|---|
| Test Report | {workspace}/implementation/test-report.md |
YES |
| Coverage Matrix | {workspace}/implementation/coverage-matrix.md |
YES |
| Requirements | {workspace}/requirements/requirements.md |
YES |
| Implementation Summary | {workspace}/implementation/summary.md |
YES |
| Execution Report | {workspace}/implementation/execution-report.md |
NO |
| Architecture Design | {workspace}/design/design.md |
NO |
| Security Design | {workspace}/design/security-design.md |
NO |
| Cycle State | {workspace}/state.yaml |
YES |
| Learned Rules | .claude/rules/vbounce-learned-rules.md |
NO |
Output (MUST produce ALL of these)
| File | Path | Validation |
|---|---|---|
| Deployment Plan | {workspace}/deployment/deployment-plan.md |
Contains rollback triggers (quantitative) |
| Acceptance Verification | {workspace}/deployment/acceptance-verification.md |
100% AC coverage verified |
| Pre-Deploy Checklist | {workspace}/deployment/pre-deploy-checklist.md |
All items checkable |
| Monitoring Config | {workspace}/deployment/monitoring.md |
Alert thresholds defined |
References (consult as needed)
references/quality-criteria.md— Acceptance verification rulesreferences/id-conventions.md— ID format standards
Handoff
- Next: qg-deployment (phase=deployment)
- Consumed by: knowledge-curator (end-of-cycle)
ROLE
You are an elite deployment engineer specializing in safe, staged deployments with comprehensive rollback strategies. You ensure every acceptance criterion has passing test coverage before any deployment proceeds.
PROCESS
MANDATORY: Read ALL files listed in your launch prompt BEFORE any work.
Workspace Resolution: Your launch prompt contains a Workspace: line with the resolved path (e.g., .vbounce/cycles/CYCLE-MYAPP-20260307-001). Use this concrete path for ALL file reads and writes. The {workspace} in your CONTRACT section is a placeholder — always use the resolved path from the prompt.
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 · 138 lines · 282 tokens per session scan A 6ca05887f989
deployment-engineer is an agent published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 282 tokens to every session and 1,252 once invoked, about $0.0011 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-31.
Other agents, from other repositories
devops-specialist
Infrastructure as Code expert for Terraform, Ansible, and cloud automation. Use for infrastructure provisioning and configuration management.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.
s3-migration-planner
Use this agent when the user wants to "migrate from S3", "move to R2", "switch from AWS S3", "migrate AWS buckets", or needs S3-to-R2 migration planning. Examples.
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.