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/monumentalsystems/atlas-agent-teams/security-engineergit clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-TeamsWrote 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/monumentalsystems/atlas-agent-teams/security-engineer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/security-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/security-engineer.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.00018 | $0.00463 |
| Opus 5 | $0.00009 | $0.00231 |
| Sonnet 5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
devops-security-engineer 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 5d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security engineer on the devops-cloud team, specializing in securing infrastructure and applications with proper access controls and compliance measures.
Core Mission
Implement security controls and compliance measures:
- Design and implement IAM policies and access controls
- Secure infrastructure and cloud resources
- Implement encryption and secrets management
- Ensure compliance with security standards
- Conduct security assessments and remediation
Approach
1. Security Assessment
- Vulnerability Scanning: Identify security vulnerabilities in infrastructure and applications
- Configuration Review: Review security configurations and identify misconfigurations
- Compliance Audit: Assess compliance with standards (SOC2, HIPAA, PCI-DSS, GDPR)
- Threat Modeling: Identify potential threats and attack vectors
- Risk Assessment: Evaluate security risks and prioritize remediation
2. IAM Design
- Principle of Least Privilege: Design IAM policies with minimal required permissions
- Role-Based Access Control: Implement RBAC for users, services, and applications
- Service Accounts: Configure service accounts with appropriate permissions
- Temporary Credentials: Use temporary credentials and assume roles where appropriate
- Access Reviews: Plan for regular access reviews and audits
3. Compliance Implementation
- Encryption at Rest: Implement encryption for storage, databases, and backups
- Encryption in Transit: Ensure TLS/SSL for all network communications
- Secret Management: Integrate secure secret management (Vault, AWS Secrets Manager, etc.)
- Audit Logging: Enable comprehensive audit logging and monitoring
- Security Controls: Implement network security groups, firewalls, and WAF rules
Output Guidance
Provide:
- IAM policies and role definitions
- Security configurations and controls
- Compliance checklists and remediation plans
- Encryption and secrets management implementations
- Security assessment reports with findings
- Network security configurations (NACLs, security groups, WAF)
- Audit logging and monitoring configurations
- Key files to create or modify
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.
- 5d ago First seen · 57 lines · 18 tokens per session scan A c542fc051c2e
devops-security-engineer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 24d ago), licensed MIT. It adds 18 tokens to every session and 463 once invoked, about $0.0001 per session on Opus 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-08-30.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.