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/quality-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/quality-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/quality-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/quality-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.00606 |
| Opus 5 | $0.00000 | $0.00303 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
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 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Agent
Languages: English | 日本語
Agent deep dive · User Guide › Agents › deep dives · Technical reference: quality-agent
The amadeus-quality-agent is your QA engineer and performance specialist. It defines test strategy, generates test suites (unit, integration, contract, security), validates coverage against acceptance criteria, designs and executes load tests, and validates non-functional requirement targets. It ensures every implemented unit meets its acceptance criteria and the overall system meets quality gates.
The amadeus-quality-agent leads two stages — one in Construction and one in Operation — and supports two additional stages. It has Bash access for running build tools, test commands, and performance testing utilities.
Stages Led
| Stage | Phase | Description |
|---|---|---|
| 3.6 Build and Test | Construction | Runs build, generates and executes test suites, validates quality gates |
| 4.6 Performance Validation | Operation | Load testing, NFR validation matrix, capacity planning |
Stages Supported
| Stage | Phase | Contribution |
|---|---|---|
| 2.2 Practices Discovery | Inception | Surfaces testing posture and quality practices from existing code |
| 3.2 NFR Requirements | Construction | Defines testable quality attribute scenarios |
What to Expect
When the amadeus-quality-agent is active, it generates build instructions and test suites, then executes them against the implemented code. During Build and Test, it runs the project's build system, executes unit tests, integration tests, and any additional test types appropriate for the project. It reports pass/fail results, coverage metrics, and quality gate status.
During Performance Validation in the Operation phase, it designs and executes load tests, validates NFR targets (latency percentiles, throughput, availability), and produces an NFR validation matrix comparing targets to actuals.
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 · 42 lines · 0 tokens per session scan A 80821502402f
quality-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 606 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
dispatcher-unification-design
Status: phase-2 design drafted; implementation is held for maintainer review. Load when: working on blockverdict transaction dispatch, or on any "single-tx diverges from multi-tx" false-reject.
red-team-reviewer
Adversarial reviewer that audits epic Success Criteria → story Done Definition coverage and attacks preplanning story maps for cross-story blind spots, implicit assumptions, and interaction gaps across 8 taxonomy categories. Requires opus.
foundation_architecture
Status: Draft Purpose: Define the minimal viable system architecture and cross‑reference OpenHands SDK capabilities with Tier 0 questions to guide incremental development. Related: ./openhandsinsightsandprioritization.md, ./implementationquestions.md, ./design/multiagentorchestration.md.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.
oracle-reviewer
Web3-DeFi specialist pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off Critical/High mitigations before senior-dev claims tasks.