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/devsecops-agentgit clone --depth 1 https://github.com/amadeus-dlc/amadeusWhat 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.00596 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
devsecops-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 2d 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.
DevSecOps Agent
Languages: English | 日本語
Agent deep dive · User Guide › Agents › deep dives · Technical reference: devsecops-agent
The amadeus-devsecops-agent is your security engineer. It ensures that security is embedded into every phase of the lifecycle rather than bolted on at the end. It takes compliance requirements identified in Ideation and implements them as security controls, threat models, scanning pipelines, and runtime monitoring. It covers application security, cloud security, and pipeline security.
Like the amadeus-compliance-agent, the amadeus-devsecops-agent operates exclusively in a support role. It contributes security expertise across five stages spanning Inception, Construction, and Operation. It has Bash access for running security scanning tools.
Stages Led
The amadeus-devsecops-agent does not lead any stages.
Stages Supported
| Stage | Phase | Contribution |
|---|---|---|
| 2.2 Practices Discovery | Inception | Security practices and scanning conventions for affirmation |
| 3.2 NFR Requirements | Construction | Security controls, threat model, STRIDE analysis |
| 3.4 Infrastructure Design | Construction | IAM policy review, security group validation |
| 3.6 Build and Test | Construction | SAST/DAST scans, dependency vulnerabilities, IaC linting |
| 4.2 Environment Provisioning | Operation | Security posture validation (Security Hub, Inspector, GuardDuty) |
What to Expect
When the amadeus-devsecops-agent is active (as a supporting agent), it focuses on attack surfaces, trust boundaries, and security controls. It reviews designs for security anti-patterns, validates that sensitive data flows are encrypted and access-controlled, and assesses third-party dependencies for known vulnerabilities.
How It Collaborates
The amadeus-devsecops-agent receives regulatory requirements from the amadeus-compliance-agent and system designs from the amadeus-architect-agent. It works with the amadeus-developer-agent on secure coding practices, the amadeus-aws-platform-agent on infrastructure hardening, and the amadeus-quality-agent on security test requirements. Its security gates and scanning configurations are handed off to the amadeus-pipeline-deploy-agent.
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A 76790a0acf96
devsecops-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 596 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.