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 skills add wedabro/bro-skills --skill speckit.devopsgit clone --depth 1 https://github.com/wedabro/bro-skillsWrote 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/wedabro/bro-skills/speckit.devops)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.devops"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.devops.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.1 | $0.00018 | $0.00784 |
| Opus 5 | $0.00009 | $0.00392 |
| Sonnet 5 | $0.00004 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
speckit.devops scanned grade A with 1 finding 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 6d 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.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- `USER node` or `USER appuser` (DO NOT run as root) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Mission
Set up and manage a standardized and secure Docker system for the project. Published ports MUST always be configured via environment variables.
📥 Input
.agents/memory/constitution.md(port configuration, security rules)- Existing
Dockerfile,docker-compose.yml(if available) .env.example
📋 Protocol
1. Port Allocation (ENV-first) ⭐
ALWAYS configure ports via ENV:
.envfile (local) or server ENV (production)docker-compose.ymlreads:"${PUBLIC_PORT}:${WEB_CONTAINER_PORT}"- Document required port variables in
.env.example; do not hide missing configuration behind a fixed fallback. - CRITICAL: If
.envor system environment already has port variables defined (e.g.PUBLIC_PORT,ADMIN_PORT,API_PORTor equivalents), ABSOLUTELY SKIP port scanning/assignment and NEVER overwrite the existing port configuration.
Port scanning rules according to environment:
| Environment | Existing Ports in .env? | Docker running? | Act |
|---|---|---|---|
| Any | ✅ Yes | Any | SKIP scan — use existing ports, DO NOT overwrite |
| Local | ❌ No | ❌ No (first time) | Scan available ports with socket/helper → select 3 consecutive empty ports |
| Local | ❌ No | ✅ Already running | SKIP scan — use current ports from docker/containers |
| Staging/Beta/Prod | ❌ No | Any | ALWAYS initial scan for configuration → write to .env |
Check Docker is running (Local):
docker compose ps --format json 2>$null
# There are containers → SKIP port scan
# Empty/error → RUN port scan
- Pattern: Public FE
N→ Admin FEN+1→ Backend APIN+2
2. Local Docker (docker-compose.yml):
- Published and container ports read from ENV:
"${PUBLIC_PORT}:${WEB_CONTAINER_PORT}" - Volume mounts cho hot-reload code
- Named volumes for
node_modules(avoid host-container lock) - Health checks for each service
3. Production Docker (docker-compose.prod.yml):
- Multi-stage builds (builder → runner)
USER nodeorUSER appuser(DO NOT run as root)- Remove devDependencies in the final image
- Alpine/Slim base images
- Ports read from ENV (NO hard-code)
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.
- 6d ago First seen · 78 lines · 18 tokens per session scan A d94945397ce7
speckit.devops is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 784 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
opencode-sandbox
Run OpenCode in a docker-dev sandbox (SSH/gh on by default; --no-ssh/--no-github to isolate). Prints docker exec attach; kept until you confirm rm. Don't use for opencode.ai (opencode-runner), Herdr, or the app.
kubernetes-skill
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and…
datarobot-workload-api
Use when the user wants to create, configure, scale, debug, observe, or roll out container workloads on DataRobot's Workload API. Triggers include: deploying a container as a managed service, listing/starting/stopping workloads, changing replica counts or autoscaling, picking CPU/GPU compute bundles, injecting…
azure-kubernetes-service
Expert knowledge for Azure Kubernetes Service (AKS) development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using AKS Fleet, GPUs, Istio/KEDA/Dapr, KAITO/Ray AI workloads…
azure-defender-for-cloud
Expert knowledge for Azure Defender For Cloud development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when securing VMs, containers/Kubernetes, SQL, storage, multicloud…
azure-aks-edge-essentials
Expert knowledge for Azure Kubernetes Service Edge Essentials development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when deploying AKS Edge/Hybrid with Arc, Azure Local…