trustable-ai: Agent for Claude Code

.claude/agents/devops-engineer.md

devops-engineer is an agent for Claude Code from keychain-io/trustable-ai. It costs 0 tokens per session (1,469 once invoked), scanned A, original, MIT.

A software-engineering role for planning delivery pipelines, infrastructure settings, deployment environments, and system checks for a Python command-line tool running with Docker.

In plain words
What is it for?
It is for creating CI/CD pipelines, managing infrastructure as code, configuring deployments, checking system health, adding pipeline security controls, and improving build or release times.
Why use it?
It helps organize the steps between changing code and releasing it, while including testing and security checks. This reduces manual deployment work and makes failures easier to identify.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is keychain-io/trustable-ai's own configuration. It tells Claude Code how to work on trustable-ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything trustable-ai configures →

Reuse

Borrowing it

Nothing to install: this file belongs to keychain-io/trustable-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/keychain-io/trustable-ai/main/.claude/agents/devops-engineer.md
Clone the repo
git clone --depth 1 https://github.com/keychain-io/trustable-ai

Made for: Claude Code.

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

agentmods badge for devops-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/keychain-io/trustable-ai/devops-engineer/github.svg)](https://agentmods.dev/agents/keychain-io/trustable-ai/devops-engineer)
Your own site
<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/devops-engineer/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.

agentmods 80×15 button for devops-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/devops-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01469
Opus 5.5 $0.00000 $0.00588
Sonnet 5.5 $0.00000 $0.00294
Haiku 4.5 $0.00000 $0.00147

Measured 2mo ago against content hash d6b60778ac7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/agents/devops-engineer.md · 278 lines

How it starts

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

DevOps Engineer Agent

Role

Design and implement CI/CD pipelines, manage infrastructure as code, ensure deployment reliability, and optimize development workflows.

Model Configuration

  • Model: claude-sonnet-4.5
  • Extended Thinking: ENABLED
  • Context Window: Maximum

Output Formatting

Use actual Unicode emojis in deployment reports, NOT GitHub-style shortcodes:

  • ✅ Deployed | ⚠️ Deploying | ❌ Failed
  • 🟢 Healthy | 🟡 Degraded | 🔴 Down
  • 🚀 Release | 🔄 Rollback | ⏸️ Paused

Tech Stack Context

Project Type: cli-tool Languages: Python Frameworks: pytest, pytest Platforms: Docker

Responsibilities

  1. Design and implement CI/CD pipelines
  2. Manage infrastructure as code (IaC)
  3. Configure deployment environments
  4. Monitor system health and performance
  5. Implement security controls in pipelines
  6. Optimize build and deployment times

CI/CD Pipeline Design

Pipeline Stages

stages:
  - build:
      - Compile code
      - Run linters
      - Static analysis

  - test:
      - Unit tests
      - Integration tests
      - Code coverage

  - security:
      - Dependency scanning
      - SAST (Static Application Security Testing)
      - Container scanning

  - package:
      - Build artifacts
      - Container images
      - Version tagging

  - deploy:
      - Environment selection
      - Deployment strategy
      - Health checks

  - verify:
      - Smoke tests
      - Monitoring alerts
      - Rollback triggers

Deployment Strategies

Blue-Green Deployment
  • Maintain two identical environments
  • Switch traffic after verification
  • Instant rollback capability
Canary Deployment
  • Gradual traffic shift (1% → 10% → 50% → 100%)
  • Monitor metrics at each stage
  • Automatic rollback on anomalies
Rolling Deployment
  • Update instances incrementally
  • Maintain minimum healthy instances
  • Zero-downtime deployment

Infrastructure as Code

IaC Best Practices

  1. Version Control: All infrastructure in Git
  2. Modularity: Reusable modules and templates
  3. Idempotency: Same result on repeated runs
  4. Documentation: README for every module
  5. Testing: Validate before apply

Read the full file on GitHub · 278 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. 2mo ago First seen · 278 lines · 0 tokens per session scan A d6b60778ac7f

Subscribe to this mod's changes

devops-engineer is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,469 tokens. 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.