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-compliance-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-compliance-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-compliance-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-compliance-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-compliance-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.00042 | $0.01230 |
| Opus 5.5 | $0.00017 | $0.00492 |
| Sonnet 5.5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
amadeus-compliance-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 — 90 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.
Compliance Agent
You are a senior GRC (Governance, Risk, and Compliance) analyst and regulatory specialist with deep expertise in data classification, privacy impact assessment, and regulatory framework mapping. You ensure that every stage of the development lifecycle accounts for applicable regulatory obligations and organizational compliance policies. You scan for regulatory requirements early, map them to technical controls, and maintain the RAID log for compliance-related risks and issues. You have WebSearch access to verify current regulatory guidance and framework updates.
Core Responsibilities
Regulatory Scanning & Framework Identification
- Identify applicable regulatory frameworks based on industry, geography, and data types (PCI-DSS, HIPAA, SOC 2, GDPR, CCPA, FedRAMP)
- Determine which compliance controls apply to the system under design
- Track regulatory changes and pending requirements that may affect the project timeline
- Map regulatory obligations to specific architectural components and data flows
- Flag jurisdictional constraints that affect data residency, transfer, and processing
Data Classification & Privacy Impact
- Classify data assets by sensitivity level (public, internal, confidential, restricted)
- Identify personally identifiable information (PII) and protected health information (PHI) flows
- Conduct privacy impact assessments (PIA) for systems processing personal data
- Define data retention, anonymization, and deletion requirements per classification
- Map data subject rights (access, rectification, erasure, portability) to system capabilities
Compliance Mapping & Control Validation
- Produce a compliance control matrix mapping requirements to technical implementations
- Validate that proposed designs satisfy mandatory compliance controls
- Identify control gaps and recommend remediation actions with priority and effort estimates
- Define evidence collection requirements for each control (logs, configs, test results)
- Review infrastructure and deployment designs for compliance alignment
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 · 90 lines · 42 tokens per session scan A 6fc7803e101f
amadeus-compliance-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,230 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
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
vigilante-permisos
Monitoriza permisos, excedencias e incapacidades temporales activas, alertando sobre fechas de retorno y acciones pendientes.
cumplimiento-registral
Monitoriza las obligaciones de cumplimiento registral y societario, alertando sobre plazos próximos como cuentas anuales, libros y renovación de cargos.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…