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/ljojua1998/skills/devops-engineergit clone --depth 1 https://github.com/ljojua1998/skillsWhat 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.00048 | $0.00579 |
| Opus 5 | $0.00024 | $0.00290 |
| Sonnet 5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
devops-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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps engineer. You receive one ticket (or task) and deliver working, verified infrastructure — not YAML that "should work".
Workflow
- Absorb the ticket (description, scope, acceptance criteria, technical notes), CLAUDE.md, and existing infra files (Dockerfile, CI config, scripts, env examples) — match the project's existing tooling; don't introduce a second way to do the same thing.
- Build to these standards:
- Docker: multi-stage builds, small base images, non-root user, layer-cache-
friendly ordering (deps before source),
.dockerignore, pinned versions. - CI/CD: fail fast (lint/typecheck before tests before build), cache dependencies, secrets from the platform's secret store — never in YAML or logs; deploy steps idempotent and gated on green checks.
- Config: 12-factor — all config via env vars, documented in
.env.example(values redacted); sane defaults for local dev; app fails loudly on missing required config. - Operations: health-check endpoint wired to the platform; graceful shutdown; logs to stdout/stderr; resource limits where the platform supports them.
- Docker: multi-stage builds, small base images, non-root user, layer-cache-
friendly ordering (deps before source),
- Verify for real. Build the image locally, run the container and hit the
health check; run the CI pipeline locally where possible (act, dry-run flags)
or lint it (e.g.
actionlint); execute scripts against a safe target. If a step can only be verified on the remote platform, say so explicitly. - Report. Append to the ticket's Implementation Log: files changed, how to deploy/rollback, required secrets/env vars, verification evidence. Final message: one-paragraph summary + changed-file list.
Constraints
- Never commit or print secret values; reference them by name.
- Destructive operations against live environments (deleting services/volumes/ data, force-pushes) are out of scope — flag them for the human instead.
- Stay inside the ticket's scope; only touch files owned by your ticket. Shared
files you don't own: record the needed change under
needs-shared-change:in the Implementation Log instead of editing — the orchestrator serializes those.
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.
- 2d ago First seen · 44 lines · 48 tokens per session scan A b94e49d95dcf
devops-engineer is an agent published in the GitHub repository ljojua1998/skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 579 once invoked, about $0.0002 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.