Borrowing it
Nothing to install: this file belongs to systemowiec/ai-agents-workspace-starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/systemowiec/ai-agents-workspace-starter/main/.agents/skills/infra-patterns/SKILL.mdgit clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starterWrote 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/skills/systemowiec/ai-agents-workspace-starter/infra-patterns)<a href="https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/infra-patterns"><img src="https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/infra-patterns/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.
<a href="https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/infra-patterns"><img src="https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/infra-patterns.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00708 |
| Opus 5 | $0.00010 | $0.00354 |
| Sonnet 5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
infra-patterns 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Infra Patterns
Patterns and templates for infra development. Read when configuring Docker, CI/CD, servers.
docker-compose.yml Service Template
Key properties for each service:
build.context: ..,dockerfile: infra/{service}/Dockerfile,target: developmentcontainer_name: ${PROJECT_NAME:-app}-{service}restart: unless-stoppedports: env-based (e.g.${SERVICE_PORT:-8080}:8080)volumes: source code bind mount with:cachedenvironment:DATABASE_URL,REDIS_URLusing service hostnames (not localhost)depends_on: withcondition: service_healthyhealthcheck: test, interval 30s, timeout 5s, retries 3, start_period 10snetworks:app-network- Resource limits:
mem_limit,cpus
Dockerfile Multi-Stage Template
3 stages:
- builder -
python:3.12-slim, install deps with--no-cache-dir --prefix=/install - development - non-root user (
appuser), copy from builder, hot reload (--reload) - production - minimal,
USER appuser,HEALTHCHECK CMD,--workers 4
Key rules:
- Always create non-root user:
groupadd -r appuser && useradd -r -g appuser appuser - Production:
USER appuserbefore CMD - Include
HEALTHCHECKin production stage
Makefile Target Template
- Pattern:
.PHONY: target+$(COMPOSE) exec backend <command> - Every target has a
## Descriptioncomment formake help
Requirements Policy
When CI/CD or multiple environments are added:
- Split:
requirements/base.txt,requirements/dev.txt,requirements/prod.txt dev.txtandprod.txtstart with-r base.txt- Production containers install ONLY
prod.txt - Dev containers install
dev.txt(pytest, ruff, mypy, factory-boy) - NEVER install test tools in production
.env Best Practices
- Unique ports per project (avoid collisions):
BACKEND_PORT,DB_PORT,REDIS_PORT - Unique volume and network names (auto from
${PROJECT_NAME}) - Secrets: NEVER commit
.env, generate withopenssl rand -hex 32
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.
- 9d ago First seen · 70 lines · 21 tokens per session scan A 70e04cae6767
infra-patterns is a skill published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 708 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-31.
Other skills, from other repositories
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
devops
DevOps - Docker, CI/CD, cloud infra, monitoring.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
devops-automator
Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use…
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.