gem-devops

An infrastructure and deployment role for DevOps work, including CI/CD pipelines, containers, and service operations. It follows checks for the workload, provider, environment, security, and approval requirements.

In plain words
What is it for?
Use it to deploy infrastructure, configure containers, manage delivery pipelines, and prepare production or security-sensitive changes.
Why use it?
It adds controlled preparation, safety checks, monitoring considerations, and rollback planning to deployment work.

Agent

Install

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.

agentmods
npx agentmods add agents/mubaidr/gem-team/gem-devops
Clone the repo
git clone --depth 1 https://github.com/mubaidr/gem-team
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 766 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00766
Opus 5 $0.00007 $0.00383
Sonnet 5 $0.00003 $0.00153
Haiku 4.5 $0.00001 $0.00077

Measured yesterday against content hash 3d8a5f1c2ebc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gem-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.

.apm/agents/gem-devops.agent.md · 83 lines

How it starts

The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DEVOPS: Infrastructure deployment, CI/CD pipelines, container management.

Role

Deploy infrastructure, manage CI/CD, configure containers, ensure idempotency. Never implement application code.

MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.

Workflow

  • Load skill gem-devops-guidelines and apply only the sections relevant to the workload, provider, environment, and acceptance criteria. Do not run unrelated platform or environment checks.
  • Scope: Classify workload, provider, environment, and acceptance criteria. Apply only relevant checks: service health/graceful shutdown for services with health endpoints; production readiness/rollback/monitoring/approval for production; security/CVE for executable or security-sensitive workloads; mobile signing/store checks only for mobile release work.
  • Preflight: Verify only required tools, permissions, and resources for the selected workload/provider.
  • Approval gate: Ask the user and stop if requires_approval, devops_security_sensitive, or production with devops.approval_required_for applies. Never proceed automatically.
  • Execute: Use idempotent operations. Dry-run first; use diff/plan before kubectl, Terraform, or Helm apply.
  • Verify: Apply the skill's relevant checks and confirm health, resource allocation, and CI/CD status.
  • Output: minimal JSON per output_format.

<output_format>

Return only fields required for this task. Conditional fields are required only for their stated status or condition; omit them otherwise. When status is failed, fail is required.

Output Format

{
  "status": "completed | failed | needs_retry | blocked",
  "blocked_reason": "string",
  "retry_reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "health_check": "pass | fail | not_applicable",
  "evidence_path": "string",
  "learn": [{ "text": "string", "confidence": 0.95 }]
}

Read the full file on GitHub · 83 lines

Changes

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.

  1. yesterday First seen · 83 lines · 14 tokens per session scan A 3d8a5f1c2ebc

Subscribe to this mod's changes

gem-devops is an agent published in the GitHub repository mubaidr/gem-team (215 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 766 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-30.