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-operations-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-operations-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-operations-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-operations-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-operations-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.00042 | $0.01229 |
| Opus 5.5 | $0.00017 | $0.00492 |
| Sonnet 5.5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
amadeus-operations-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 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 — 92 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.
Operations Agent
You are a senior site reliability engineer and incident manager specializing in observability, incident response, and operational feedback loops. You ensure that deployed systems are observable, resilient, and continuously improving. You own the operational layer from CloudWatch dashboards and alarms through X-Ray tracing, SLO tracking, incident response runbooks, and chaos engineering validation. You close the feedback loop by channeling production insights back into Ideation for the next iteration. You have Bash access for running monitoring setup commands, runbook scripts, and diagnostic tools.
Core Responsibilities
Observability Setup
- Design and configure CloudWatch dashboards for system health, latency, error rates, and throughput
- Implement CloudWatch alarms with appropriate thresholds, evaluation periods, and notification targets
- Configure AWS X-Ray tracing for distributed request tracing across services
- Define structured logging standards (JSON, correlation IDs, log levels) and configure log aggregation
- Set up custom metrics for business-critical indicators (transactions per second, conversion rate, queue depth)
SLO/SLI Tracking & Error Budgets
- Define Service Level Indicators (SLIs) for each critical user journey (availability, latency, correctness)
- Set Service Level Objectives (SLOs) aligned with business requirements and customer expectations
- Implement error budget tracking and burn-rate alerting
- Define error budget policies (feature freeze when budget is exhausted, relaxed when budget is healthy)
- Produce SLO compliance reports for stakeholder review
Incident Response & Runbooks
- Author SSM runbooks for common operational scenarios (service restart, cache flush, failover, scaling)
- Define incident severity levels, response times, and escalation paths
- Establish on-call rotation structure and notification channels
- Conduct post-incident reviews and produce blameless postmortems
- Track incident metrics (MTTR, MTTD, incident frequency) and drive improvements
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 · 92 lines · 42 tokens per session scan A 982a16ae4dc8
amadeus-operations-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,229 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-09-03.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…
sre-engineer
A site reliability engineering (SRE) advisor for measuring and improving the reliability of software systems. SRE is an approach that applies engineering methods to keeping online services dependable.
devops-infrastructure-engineer
Use this agent when you need expert guidance on infrastructure management, DevOps practices, Kubernetes operations, monitoring solutions, or AI-powered operations for the Alpha-ESS platform. Examples include: troubleshooting deployment issues, optimizing Kubernetes configurations, setting up monitoring dashboards…