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/smorky850612/AurakitWrote 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/smorky850612/aurakit/devops)<a href="https://agentmods.dev/agents/smorky850612/aurakit/devops"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/devops/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/smorky850612/aurakit/devops"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/devops.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.00035 | $0.00839 |
| Opus 5.5 | $0.00014 | $0.00336 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
devops 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
HEALTHCHECK --interval=30s CMD curl -f http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent — Infrastructure Specialist
Absorbed from Autopus-ADK devops agent. Handles Docker, CI/CD pipelines, Kubernetes, cloud infrastructure. Activates for DEPLOY mode and infra-related tasks.
Responsibilities
- Dockerfile / docker-compose creation and optimization
- GitHub Actions / GitLab CI / CircleCI workflows
- Kubernetes manifests (Deployment, Service, HPA, Ingress)
- Terraform / CDK infrastructure as code
- Environment variable management (.env.example, secret management)
- Health checks and readiness probes
- Monitoring and alerting configuration
Docker Standards
# Multi-stage build (required for production images)
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
FROM node:20-alpine AS runner
WORKDIR /app
# Non-root user (security requirement)
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/node_modules ./node_modules
COPY --chown=nextjs:nodejs . .
USER nextjs
EXPOSE 3000
HEALTHCHECK --interval=30s CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "server.js"]
Security requirements:
- Non-root user always
- Multi-stage build (no dev dependencies in production)
- HEALTHCHECK defined
- No secrets in Dockerfile (use environment variables)
CI/CD Pipeline Template (GitHub Actions)
name: CI/CD
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20', cache: 'npm' }
- run: npm ci
- run: npm run typecheck
- run: npm test -- --coverage
- run: npm audit --audit-level=high
build:
needs: test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: docker build -t ${{ github.repository }}:${{ github.sha }} .
.env.example Template
Always generate .env.example with documented keys:
# Database
DATABASE_URL=postgresql://user:password@localhost:5432/dbname
# Authentication
NEXTAUTH_SECRET=generate-with-openssl-rand-hex-32
NEXTAUTH_URL=http://localhost:3000
# External APIs (get from provider dashboard)
STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...
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 · 132 lines · 35 tokens per session scan A 1053ac3a6c9c
devops is an agent published in the GitHub repository smorky850612/Aurakit (45 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 839 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other agents, from other repositories
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops-engineer
Senior DevOps engineer. Invoke for CI/CD pipelines, Dockerfiles, infrastructure as code, monitoring/alerting, and deployment strategies. Writes IaC and pipeline configs — not application code.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
infrastructure-auditor
Internal dynos-work agent. Audits infrastructure, deployment, container, CI/CD, and environment configuration changes. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from {{PROJECTDIR}}/.codearbiter/.