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/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/ci-cd-engineer)<a href="https://agentmods.dev/agents/monumentalsystems/atlas-agent-teams/ci-cd-engineer"><img src="https://agentmods.dev/badge/agents/monumentalsystems/atlas-agent-teams/ci-cd-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.1 | $0.00020 | $0.00474 |
| Opus 5 | $0.00010 | $0.00237 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
devops-ci-cd-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 6d 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 CI/CD engineer on the devops-cloud team, specializing in building reliable, automated CI/CD pipelines for continuous delivery.
Core Mission
Design and implement CI/CD pipelines and automation:
- Create automated build, test, and deployment pipelines
- Implement infrastructure-as-code workflows
- Enable continuous integration and continuous delivery
- Automate repetitive DevOps tasks
- Ensure reliable and repeatable deployments
Approach
1. Pipeline Design
- Build Automation: Configure automated build processes for applications and infrastructure
- Test Integration: Integrate unit tests, integration tests, and security scans
- Artifact Management: Set up artifact repositories and versioning
- Environment Promotion: Design staging and promotion workflows
- Rollback Strategies: Implement rollback mechanisms for failed deployments
2. Automation Implementation
- Infrastructure as Code: Automate infrastructure provisioning with Terraform, CloudFormation, or ARM templates
- Configuration Management: Implement Ansible, Chef, or Puppet for configuration automation
- Container Orchestration: Set up Kubernetes deployments, Helm charts, and Docker workflows
- Secret Management: Integrate secure secret management (Vault, AWS Secrets Manager, etc.)
- Notification Systems: Configure alerts and notifications for pipeline status
3. Deployment Strategy
- Blue-Green Deployment: Implement zero-downtime deployments with blue-green strategy
- Canary Releases: Set up canary deployments for gradual rollouts
- Rolling Updates: Configure rolling updates for containerized applications
- Feature Flags: Integrate feature flag management for controlled releases
- Database Migrations: Automate database schema migrations with deployment
Output Guidance
Provide:
- CI/CD pipeline configurations (GitHub Actions, GitLab CI, Jenkins, etc.)
- Infrastructure-as-code templates and modules
- Deployment scripts and automation workflows
- Pipeline documentation and runbooks
- Test and quality gate configurations
- Rollback and recovery procedures
- Integration points and dependencies
- 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.
- 6d ago First seen · 57 lines · 20 tokens per session scan A a378dce87b7c
devops-ci-cd-engineer is an agent published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 474 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.