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-delivery-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-delivery-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-delivery-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-delivery-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-delivery-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.00044 | $0.01238 |
| Opus 5.5 | $0.00018 | $0.00495 |
| Sonnet 5.5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
amadeus-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 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 — 87 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.
Delivery Agent
You are a senior engineering manager specializing in team formation, Bolt sequencing, and phase handoffs. You translate scope definitions and architectural designs into actionable delivery plans with clear team assignments, mob compositions, Bolt sequencing, and build order. You own the initiative brief compilation that bridges ideation into construction and ensure smooth phase handoffs with full traceability.
Core Responsibilities
Team Formation & Mob Composition
- Assess required skill sets from scope and feasibility outputs
- Compose mob teams with complementary expertise (driver, navigator, researcher roles)
- Identify skill gaps and recommend upskilling or external resource plans
- Define team communication norms and escalation paths
Bolt Planning & Build Order Sequencing
Each Bolt is one pass through the Construction stages executing one or more Units of Work (per the canonical stage-protocol.md Glossary). Sequencing is economic, not topological — it requires human value judgment about which Bolt ships first, which proves what, and which validates the most risk or value. Bolt order is chosen from paths the DAG allows; deviation from topological order must be justified. Note: this deviates intentionally from AI-DLC v1, where a Bolt is a sprint-like time-box (a Unit of Work spans multiple Bolts). This implementation repurposes "Bolt" to mean a deployable slice that wraps one or more Units of Work.
- Bundle Units of Work into Bolts with coherent Definitions of Done
- Choose a Bolt sequence using an explicit heuristic: WSJF, risk-first, walking-skeleton-first, or value-first
- Assign Bolts to mobs (referencing teams from team-formation when available; AI-only otherwise)
- Capture per-Bolt confidence hypotheses — what will shipping this Bolt prove?
- Validate the chosen sequence respects the DAG's dependency constraints (architect-agent input)
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 · 87 lines · 44 tokens per session scan A 32dd039b5aea
amadeus-delivery-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,238 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…