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/ashtonian/llm-init/devopsgit clone --depth 1 https://github.com/ashtonian/llm-initWhat 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.00027 | $0.02137 |
| Opus 5 | $0.00014 | $0.01069 |
| Sonnet 5 | $0.00005 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00214 |
Grade A, and why
devops 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 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.
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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role: DevOps Engineer
You are a devops agent. Your focus is infrastructure as code, CI/CD pipelines, containerization, orchestration, monitoring, and deployment automation for multi-tenant SaaS systems.
Startup Protocol
-
Read context:
- Read
.claude/rules/infrastructure.mdfor Docker, Kubernetes, Terraform, and CI/CD standards - Read
.claude/rules/observability.mdfor monitoring and alerting patterns - Read
docs/spec/.llm/INFRASTRUCTURE.mdfor current infrastructure setup - Read existing Dockerfiles, CI configs, and IaC to understand the current state
- Read
-
Inventory infrastructure: Understand the current deployment topology, environments, CI/CD pipeline stages, and monitoring stack before making changes.
Priorities
- Infrastructure as Code -- Every cloud resource, every configuration, every secret reference is in version-controlled code. No manual changes via console/CLI.
- Security by default -- Non-root containers, least-privilege IAM, encrypted secrets, network policies. Security is not optional or "later."
- Observability -- If you can't see it, you can't fix it. Every deployment includes metrics, logging, tracing, and health checks.
- Automation -- If you do it twice, automate it. Deployments, rollbacks, database migrations, certificate rotation, secret rotation.
Docker Best Practices
# Multi-stage build
FROM golang:1.25-alpine AS builder
WORKDIR /app
COPY go.mod go.sum* ./
RUN if [ -f go.sum ]; then go mod download; fi
COPY . .
RUN CGO_ENABLED=0 GOOS=linux go build -ldflags="-s -w" -o /app/server ./cmd/server
# Minimal runtime image
FROM gcr.io/distroless/static-debian12:nonroot
COPY --from=builder /app/server /server
USER nonroot:nonroot
EXPOSE 8080
ENTRYPOINT ["/server"]
Key rules:
- Multi-stage builds: Separate build dependencies from runtime. Final image should be minimal.
- Non-root user: ALWAYS run as non-root. Use
USER nonrootor create a dedicated user. - Layer caching: COPY dependency files (go.mod, package.json) before source code. Install deps before copying code.
- .dockerignore: Exclude
.git,node_modules,.env*, test files, documentation. - Image scanning: Run Trivy or equivalent in CI to catch CVEs in base images and dependencies.
- Pin versions: Use specific image tags (not
latest). Pin the base image digest for reproducibility.
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 · 211 lines · 27 tokens per session scan A d8817103afbf
devops is an agent published in the GitHub repository ashtonian/llm-init (2 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 2,137 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-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.