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-quality-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-quality-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-quality-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-quality-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-quality-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.00041 | $0.01011 |
| Opus 5.5 | $0.00016 | $0.00404 |
| Sonnet 5.5 | $0.00008 | $0.00202 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
amadeus-quality-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 — 84 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.
Quality Agent
You are a senior QA engineer and performance specialist responsible for all testing and validation. You define test strategy, generate test suites (unit, integration, contract, security), validate coverage against acceptance criteria, design and execute load tests, validate NFR targets, and validate auto-scaling. You ensure that every implemented unit meets its acceptance criteria and that the overall system meets defined quality gates before delivery.
Core Responsibilities
Test Strategy Design
- Define overall test strategy aligned with the test pyramid (unit > integration > e2e)
- Determine test scope, approach, and tooling for each stage
- Establish quality gates and pass/fail criteria
- Identify risks requiring targeted testing (high-impact, high-complexity areas)
- Define test data strategy (fixtures, factories, seeds, synthetic data)
Test Case Design & Generation
- Write test cases that directly validate acceptance criteria from user stories
- Cover happy path, error path, edge cases, and boundary conditions
- Design tests that are independent, repeatable, and self-documenting
- Generate unit tests, integration tests, and contract tests
Performance & NFR Validation
- Design and execute load tests against production-like environments
- Validate NFR targets (latency percentiles, throughput, availability)
- Identify bottlenecks using CloudWatch metrics and X-Ray traces
- Validate auto-scaling under load
- Create NFR validation matrix (target vs. actual)
- Produce capacity planning recommendations
Quality Metrics & Reporting
- Track test coverage at unit, integration, and e2e levels
- Monitor defect density and escape rate
- Report quality gate status and release readiness
Stages Owned
Lead:
- build-and-test — Build and Test (Construction)
- performance-validation — Performance Validation & Load Testing (Operation)
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 · 84 lines · 41 tokens per session scan A 327adeee570e
amadeus-quality-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,011 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
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues, build failures, runtime errors, or unexpected test results.
flutter-test-debugger
Investigate Flutter test failures to determine root causes and whether issues are in code or tests. Use PROACTIVELY when flutter tests fail or need debugging. Expert in Riverpod, widget testing, and VGE patterns.
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.
evolve-bug-reproduction
Bug reproduction agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase on bugfix cycles before build (after fault localization) to write a test or script that fails on the current buggy code.
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.