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/delivery-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/delivery-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/delivery-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/delivery-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.00519 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
delivery-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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivery Agent
Languages: English | 日本語
Agent deep dive · User Guide › Agents › deep dives · Technical reference: delivery-agent
The amadeus-delivery-agent is your engineering manager and delivery planner. It translates scope definitions and architectural designs into actionable delivery plans with team assignments, build ordering, and sequencing. It owns the initiative brief that bridges Ideation into Construction and ensures smooth phase handoffs with full traceability.
The amadeus-delivery-agent leads three stages spanning Ideation and Inception. It is the agent responsible for ensuring that what has been designed can actually be delivered, and in what order.
Stages Led
| Stage | Phase | Description |
|---|---|---|
| 1.5 Team Formation | Ideation | Assesses required skills and composes team structure |
| 1.7 Approval & Handoff | Ideation | Compiles initiative brief for phase gate approval |
| 2.8 Delivery Planning | Inception | Plans the Bolt sequence (economic ordering through 2.7's DAG), with team allocation, risk/sequencing rationale, and external dependency map |
Stages Supported
| Stage | Phase | Contribution |
|---|---|---|
| 1.4 Scope Definition | Ideation | Validates scope against delivery feasibility |
| 2.7 Units Generation | Inception | Aligns unit granularity with planning needs |
What to Expect
When the amadeus-delivery-agent is active, it focuses on sequencing and feasibility. It asks about team size, available expertise, and delivery preferences. It produces structured plans that map units of work to a build order, identify the critical path, and flag dependencies that could block progress.
How It Collaborates
The amadeus-delivery-agent receives scope and priorities from the amadeus-product-agent, and unit specifications and complexity estimates from the amadeus-architect-agent. Its delivery plan is consumed by all Construction agents to understand build order and team assignments.
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 · 41 lines · 0 tokens per session scan A dff6b698551e
delivery-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 519 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.