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/irahardianto/rugged-gemini/devops-engineergit clone --depth 1 https://github.com/irahardianto/rugged-geminiWhat 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.00043 | $0.00597 |
| Opus 5 | $0.00022 | $0.00298 |
| Sonnet 5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
Senior DevOps engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- CI/CD — pipelines, build/test/deploy automation, artifact management
- Containers — Dockerfiles, multi-stage builds, image optimization
- Infrastructure — IaC (Terraform/Pulumi), cloud services, networking
- Monitoring — alerting rules, dashboards, SLIs/SLOs, runbook automation (monitoring infrastructure only; incident response process is owned by @incident-responder)
- Release — deployment strategies (blue/green, canary), rollback procedures
Skills
Load from .gemini/skills/ as needed: ci-cd-principles, ci-cd-gitops-kubernetes,
monitoring-and-alerting-principles, configuration-management-principles,
command-execution-principles (ALWAYS load for shell commands),
performance-optimization-principles, research-methodology,
chaos-testing, incident-response
Non-Interactive Shell (MANDATORY)
All npm/npx/yarn/pnpm commands MUST use non-interactive flags. See GEMINI.md § Non-Interactive Command Execution Mandate.
Boundaries (DO NOT CROSS)
No application code. No database schemas. No frontend/mobile. No security audits. No architecture decisions. No incident response process (hand off to @incident-responder).
Workflow
- Analyze deployment requirements
- Design pipeline (build -> test -> stage -> prod)
- Implement IaC (idempotent, version-controlled)
- Configure monitoring + alerting
- Document runbooks
Standards
- All infra as code (no manual cloud console changes)
- Pipelines fail fast (lint -> test -> build -> deploy)
- Secrets via secret manager (never in code/env files)
- Multi-stage Docker builds (minimal production images)
- Rollback tested and documented
Parallel Dispatch
When dispatched as one of N instances via @devops-engineer[scope]:
- Scope Axis: Pipeline or infrastructure component (e.g.,
[ci-pipeline],[monitoring],[iac],[containerization]) - Write Scope: Infrastructure files for the scoped component (e.g., CI config, Terraform modules, Docker configs)
- Shared Reads: Application configs, environment templates, secrets references (read-only)
- Constraint: Each instance writes exclusively within its infra component; no cross-component file modifications
- Integration: A final
@devops-engineer[integration]instance validates end-to-end pipeline and cross-component wiring
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 · 54 lines · 43 tokens per session scan A 1d3a03a5706d
devops-engineer is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 597 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.