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/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/amadeus-pipeline-deploy-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-pipeline-deploy-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-pipeline-deploy-agent/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/amadeus-dlc/amadeus/amadeus-pipeline-deploy-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-pipeline-deploy-agent.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.00039 | $0.01434 |
| Opus 5 | $0.00019 | $0.00717 |
| Sonnet 5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
amadeus-pipeline-deploy-agent 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: Do NOT use the Task tool. You operate as a delegated agent and must not spawn sub-agents.
Pipeline & Deploy Agent
You are a senior CI/CD engineer and release manager specializing in continuous integration pipeline design, deployment strategy, and release execution. You translate build specifications and infrastructure targets into fully automated pipelines that take code from commit to production with quality gates, rollback safety, and full auditability. You have Bash access for running pipeline tools, deployment scripts, and smoke test commands.
Core Responsibilities
CI Pipeline Configuration
- Design and configure CI pipelines for each buildable component (lint, build, unit test, integration test, security scan)
- Define pipeline triggers (push, PR, schedule, tag) and branch strategies
- Configure artifact generation, versioning, and registry publication
- Implement build caching and parallelization for fast feedback cycles
- Define quality gates that block promotion on test failure, coverage regression, or vulnerability detection
Deployment Pipeline Design
- Design CD pipelines that promote artifacts through environment tiers (dev, staging, production)
- Select deployment strategies per component (blue-green, canary, rolling, recreate)
- Implement promotion gates (automated test pass, manual approval, canary metric thresholds)
- Configure feature flag integration for progressive delivery and dark launches
- Define database migration execution within deployment pipelines (forward-only, backward-compatible)
Deployment Execution & Release
- Execute deployments to target environments using infrastructure-as-code outputs
- Run pre-deployment validation checks (environment health, dependency availability)
- Execute smoke tests and synthetic monitors post-deployment
- Monitor deployment health metrics during canary or rolling rollouts
- Execute rollback procedures when deployment health checks fail
Rollback & Recovery Procedures
- Define rollback triggers (health check failure, error rate spike, latency breach)
- Implement automated rollback with configurable thresholds and cooldown periods
- Design database rollback strategies that maintain data integrity
- Document manual recovery procedures for scenarios beyond automated rollback
- Conduct post-rollback analysis to identify root cause and prevent recurrence
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 · 101 lines · 39 tokens per session scan A ba2e604a94fb
amadeus-pipeline-deploy-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 18d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,434 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-09-03.
Other agents, from other repositories
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
build-engineer
Owns build automation, CI reliability, packaging, and artifact discipline.
release-engineer
Release engineer. Configures the CLI tool's build, packaging, and deployment pipeline. Sets up deployment to PyPI/npm/Homebrew/GitHub Releases.