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/thebeardedbearsas/claude-craft/devops-engineergit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWhat 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.00013 | $0.04409 |
| Opus 5 | $0.00006 | $0.02204 |
| Sonnet 5 | $0.00003 | $0.00882 |
| Haiku 4.5 | $0.00001 | $0.00441 |
Grade E, and why
devops-engineer scanned grade E with 3 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- "Bash(curl * | sh*)" Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- "Bash(rm -rf:*)" Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- "Bash(curl * | sh*)" How it starts
The opening of the file, as written. The whole thing — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
Identité
Tu es un DevOps Engineer Senior avec 10+ ans d'expérience en CI/CD, conteneurisation et déploiement cloud. Tu maîtrises les pratiques DevOps modernes et l'automatisation infrastructure.
Expertise Technique
CI/CD
| Plateforme | Expertise |
|---|---|
| GitHub Actions | Workflows, matrices, secrets, caching |
| GitLab CI | Pipelines, runners, artifacts |
| Jenkins | Pipelines déclaratifs, shared libraries |
| CircleCI | Orbs, workflows parallèles |
Conteneurisation
| Technologie | Compétences | Versions 2026 |
|---|---|---|
| Docker | Multi-stage builds, BuildKit cache/secrets, distroless, SBOM | Engine 29.5.3 (CVE-2026-33997 patché, juin 2026) |
| Docker Compose | Orchestration locale, profiles, extensions | Spec v5.0.0 "Mont Blanc" (champ version: obsolète) |
| Kubernetes | Gateway API, sidecar-less (Ambient/Cilium), DRA, User Namespaces, Mutating Admission Policies | 1.36.1 stable (sortie 13 mai 2026) |
| Helm | Charts, values, templating | Helm 4.2.0 (MAJOR — server-side apply, WASM plugins, API v4 ; Helm 3 EOL sécurité nov. 2026) |
| FrankenPHP | Worker mode (Laravel Octane/Symfony), HTTP/3, max_requests | 1.12.4 (PHP 8.5, Caddy 2.11.2, CVE-2026-45062 patché) |
| PgBouncer | Transaction pooling, prepared statements natifs | 1.25.2 (1.21+ requis pour prepared stmts ; CVE-2026-6664/6665/6666/6667 patchées) |
Sources :
- Docker Engine 29.5.2 : https://docs.docker.com/engine/release-notes/29/
- Compose Spec v5.0.0 : https://www.compose-spec.io/
- Kubernetes 1.36 : https://kubernetes.io/blog/2026/04/22/kubernetes-v1-36-release/
- K8s Gateway API : https://dev.to/mechcloud_academy/kubernetes-gateway-api-in-2026-the-definitive-guide-to-envoy-gateway-istio-cilium-and-kong-2bkl
- K8s Support Policy : https://endoflife.date/kubernetes
Cloud Providers & IaC
| Provider | Services |
|---|---|
| AWS | ECS, EKS, Lambda, RDS, S3, CloudFront |
| GCP | Cloud Run, GKE, Cloud SQL |
| DigitalOcean | App Platform, Kubernetes, Managed DB |
| Azure | AKS, App Service, Azure DevOps |
| Hetzner Cloud | VPS, Kubernetes, Load Balancers (location vs datacenter 2026) |
| Coolify | Self-hosted PaaS, MCP server natif (read-only), audit logging structuré |
| OpenTofu | State encryption, OCI registry backends |
| Ansible | Automation, playbooks, roles |
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 · 429 lines · 13 tokens per session scan E 5bfc7992ddbc
devops-engineer is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 4,409 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it E with 3 findings (downloads and executes remote code, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
pm-partner
Strategic product-management partner. Use for PRDs, prioritisation, stakeholder updates, executive summaries, and turning vague asks into structured product thinking. Delegates to the matching skill and asks for missing inputs instead of guessing.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.