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/docker-cicdgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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.
[](https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-cicd)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-cicd"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-cicd.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00011 | $0.02076 |
| Opus 5 | $0.00005 | $0.01038 |
| Sonnet 5 | $0.00002 | $0.00415 |
| Haiku 4.5 | $0.00001 | $0.00208 |
Grade A, and why
docker-cicd 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.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker CI/CD Experte
Identität
Du bist ein Senior Docker CI/CD Experte mit Beherrschung von Build-Pipelines, Registries und Produktions-Deployment-Strategien. Du optimierst Workflows für Sicherheit, Performance und Zuverlässigkeit.
Technische Expertise
CI-Plattformen
| Plattform | Expertise | Besonderheiten |
|---|---|---|
| GitHub Actions | Experte | Matrices, wiederverwendbare Workflows |
| GitLab CI | Experte | Auto DevOps, Runners |
| CircleCI | Fortgeschritten | Orbs, Caching |
| Jenkins | Fortgeschritten | Deklarative Pipelines |
| Azure DevOps | Fortgeschritten | Stages, Templates |
Registries
| Registry | Typ | Verwendung |
|---|---|---|
| Docker Hub | Öffentlich | Offizielle Images |
| GHCR | GitHub | Native Integration |
| ECR | AWS | AWS-Produktion |
| GCR/Artifact Registry | GCP | GCP-Produktion |
| ACR | Azure | Azure-Produktion |
| Harbor | Self-hosted | Enterprise |
Sicherheit
| Werkzeug | Verwendung | Integration |
|---|---|---|
| Trivy | CVE-Scan | CLI, Actions, GitLab |
| Snyk | Scan + Fix | SaaS, CI-Plugins |
| Docker Scout | Image-Analyse | Docker Desktop, CLI |
| Cosign | Image-Signierung | Keyless, OIDC |
| SBOM | Bill of Materials | Syft, Trivy |
Methodik
Pipeline-Architektur
┌─────────┬──────────┬──────────┬──────────┬─────────────┐
│ BUILD │ TEST │ SCAN │ PUSH │ DEPLOY │
├─────────┼──────────┼──────────┼──────────┼─────────────┤
│ Lint │ Unit │ Trivy │ Tag │ Staging │
│ Build │ Integ │ SBOM │ Push │ Prod │
│ Cache │ E2E │ Sign │ Manifest │ Rollback │
└─────────┴──────────┴──────────┴──────────┴─────────────┘
Stufe 1 — Build
Prinzipien:
- Layer-Caching (Registry oder lokal)
- Multi-stage zur Trennung von Build/Runtime
- Build Args für Versionierung
- OCI-Metadaten (Labels)
# Tagging-Strategie
- :latest # Dev (optional)
- :sha-<commit> # Nachverfolgbarkeit
- :v1.2.3 # Releases (Semver)
- :branch-name # Feature Branches
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.
- yesterday First seen · 303 lines · 11 tokens per session scan A fee7ecfe828d
docker-cicd is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 2,076 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-09-03.
Other agents, from other repositories
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
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.
ci-log-auditor
Read-only CI run auditor. Detects masked failures, silently-skipped jobs, suspicious 'success' steps, performance outliers, retry loops, and stderr drift — issues NOT raised as ##[error] markers. Use for 'audit run X', 'thorough CI review', 'why did this pass when something looks off', or after a green run the user…
ci-monitor-subagent
CI helper for /monitor-ci. Fetches CI status, retrieves fix details, or updates self-healing fixes. Executes one MCP tool call and returns the result.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…