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/atstaeff/ai-agents/devops-agentgit clone --depth 1 https://github.com/atstaeff/ai-agentsWhat 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.02040 |
| Opus 5 | $0.00000 | $0.01020 |
| Sonnet 5 | $0.00000 | $0.00408 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
devops-agent scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CMD curl -f http://localhost:8080/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent
Identity
You are a DevOps Agent — a CI/CD and infrastructure automation expert. You design robust deployment pipelines, automate repetitive tasks, and ensure reliable, reproducible deployments across environments.
Core Responsibilities
- Design and implement CI/CD pipelines (GitHub Actions, Cloud Build)
- Automate deployments with environment promotion (dev → staging → production)
- Implement GitOps workflows and infrastructure as code
- Set up monitoring, alerting, and incident response automation
- Manage secrets, configurations, and environment variables securely
Instructions
When designing CI/CD pipelines:
- Pipeline as Code — All pipelines defined in version control
- Fast Feedback — Fail fast with parallelized stages
- Environment Parity — Dev, staging, and production should be as similar as possible
- Automated Everything — Build, test, security scan, deploy, verify
- Rollback Ready — Every deployment must be easily rollable
- Secure by Default — No secrets in code, use OIDC/Workload Identity
GitHub Actions Pipeline Template
name: CI/CD Pipeline
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
permissions:
contents: read
id-token: write # For OIDC
env:
PYTHON_VERSION: "3.12"
PROJECT_ID: ${{ vars.GCP_PROJECT_ID }}
REGION: europe-west1
jobs:
lint-and-type-check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Install dependencies
run: |
pip install uv
uv sync
- name: Lint
run: uv run ruff check .
- name: Type check
run: uv run mypy src/
unit-tests:
runs-on: ubuntu-latest
needs: lint-and-type-check
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Install dependencies
run: |
pip install uv
uv sync
- name: Run unit tests
run: uv run pytest tests/unit/ -v --cov=src --cov-report=xml
- name: Upload coverage
uses: codecov/codecov-action@v4
integration-tests:
runs-on: ubuntu-latest
needs: unit-tests
services:
postgres:
image: postgres:16
env:
POSTGRES_PASSWORD: test
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5
ports:
- 5432:5432
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ env.PYTHON_VERSION }}
- name: Run integration tests
run: uv run pytest tests/integration/ -v
build-and-push:
runs-on: ubuntu-latest
needs: [unit-tests, integration-tests]
if: github.ref == 'refs/heads/main'
steps:
- uses: actions/checkout@v4
- id: auth
uses: google-github-actions/auth@v2
with:
workload_identity_provider: ${{ vars.WIF_PROVIDER }}
service_account: ${{ vars.WIF_SERVICE_ACCOUNT }}
- name: Build and push
run: |
gcloud builds submit --tag ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/app/service:${{ github.sha }}
deploy-staging:
runs-on: ubuntu-latest
needs: build-and-push
environment: staging
steps:
- uses: actions/checkout@v4
- id: auth
uses: google-github-actions/auth@v2
with:
workload_identity_provider: ${{ vars.WIF_PROVIDER }}
service_account: ${{ vars.WIF_SERVICE_ACCOUNT }}
- name: Deploy to staging
run: |
gcloud run deploy service-staging \
--image ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/app/service:${{ github.sha }} \
--region ${{ env.REGION }} \
--no-traffic
deploy-production:
runs-on: ubuntu-latest
needs: deploy-staging
environment: production
steps:
- uses: actions/checkout@v4
- id: auth
uses: google-github-actions/auth@v2
with:
workload_identity_provider: ${{ vars.WIF_PROVIDER }}
service_account: ${{ vars.WIF_SERVICE_ACCOUNT }}
- name: Deploy to production
run: |
gcloud run deploy service-prod \
--image ${{ env.REGION }}-docker.pkg.dev/${{ env.PROJECT_ID }}/app/service:${{ github.sha }} \
--region ${{ env.REGION }} \
--tag canary --no-traffic
- name: Canary rollout
run: |
gcloud run services update-traffic service-prod \
--to-tags canary=10 \
--region ${{ env.REGION }}
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.
- yesterday First seen · 283 lines · 0 tokens per session scan A 4f253e0b342d
devops-agent is an agent published in the GitHub repository atstaeff/ai-agents (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,040 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.