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 agents/amadeus-dlc/amadeus/operations-agentgit 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/operations-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/operations-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/operations-agent.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.00000 | $0.00686 |
| Opus 5 | $0.00000 | $0.00343 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
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 3d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Agent
Languages: English | 日本語
Agent deep dive · User Guide › Agents › deep dives · Technical reference: operations-agent
The amadeus-operations-agent is your site reliability engineer and incident manager. It ensures that deployed systems are observable, resilient, and continuously improving. It owns the operational layer from CloudWatch dashboards and alarms through X-Ray tracing, SLO tracking, incident response runbooks, and chaos engineering validation. Critically, it closes the feedback loop by channeling production insights back into Ideation for the next iteration.
The amadeus-operations-agent leads three stages in the Operation phase. It has Bash access for running monitoring setup commands, runbook scripts, and diagnostic tools.
Stages Led
| Stage | Phase | Description |
|---|---|---|
| 4.4 Observability Setup | Operation | Dashboards, alarms, tracing, structured logging, custom metrics |
| 4.5 Incident Response | Operation | SSM runbooks, incident plan, escalation matrix, on-call structure |
| 4.7 Feedback & Optimization | Operation | SLO reports, cost analysis, drift detection, feedback loop |
The amadeus-quality-agent leads 4.6 Performance Validation; the operational telemetry and baselines this agent sets up in 4.4 feed that work informally, but it is not a formal support agent on 4.6.
Stages Supported
None. The amadeus-operations-agent is a lead-only agent — it supports no other agent's stages. Its leads all fall in Operation, where it closes the lifecycle loop.
What to Expect
When the amadeus-operations-agent is active, it asks about your monitoring preferences, SLO targets, incident response processes, and on-call structure. It produces CloudWatch dashboard configurations, alarm definitions with thresholds and notification targets, X-Ray tracing setup, SSM runbooks for common scenarios (service restart, cache flush, failover), and incident severity definitions with escalation paths.
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A c37623af8247
operations-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 686 tokens. 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
requirements-analyst
Use this agent when decomposing, analyzing, and validating requirements across the SDD workflow. Specializes in requirements engineering, traceability analysis, coverage mapping, and quality validation - focuses on requirements methodology rather than code implementation.
traceability-auditor
Use this agent to verify cross-layer traceability and project-wide document integrity across the SDD flow. A READ-ONLY mechanical gate: it runs the traceability/validation tooling and reports gaps, broken links, ID/naming violations, and orphaned artifacts. It reports only — it does not fix. A downstream-heavy role…
OWL-IMPLEMENTATION
Status: ✅ Implemented Script: scripts/owl.py Wrapper: scripts/owl.
owl-of-athena
Archive management agent for Athena. Handles athena-index.md maintenance, archived feature retrieval, search, and progress pruning. Dispatch when user asks about archived features, wants to search history, or a feature completes.
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.