Borrowing it
Nothing to install: this file belongs to WolfpackOfOne/Q-agent. 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/WolfpackOfOne/Q-agent/main/.claude/skills/docker-workflow/SKILL.mdgit clone --depth 1 https://github.com/WolfpackOfOne/Q-agentWrote 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/wolfpackofone/q-agent/docker-workflow)<a href="https://agentmods.dev/skills/wolfpackofone/q-agent/docker-workflow"><img src="https://agentmods.dev/badge/skills/wolfpackofone/q-agent/docker-workflow/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/wolfpackofone/q-agent/docker-workflow"><img src="https://agentmods.dev/badge/skills/wolfpackofone/q-agent/docker-workflow.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.00050 | $0.02266 |
| Opus 5.5 | $0.00020 | $0.00906 |
| Sonnet 5.5 | $0.00010 | $0.00453 |
| Haiku 4.5 | $0.00005 | $0.00227 |
Grade A, and why
docker-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Workflow Skill
Handle Q-agent's Docker image: build, smoke-test, push, verify. The image
bundles LEAN CLI + infrastructure pipelines + marimo in a single
linux/amd64 image, published to ghcr.io/wolfpackofone/q-agent on every
push to main by .github/workflows/docker.yml.
When to invoke
- "bump LEAN to X.Y.Z" / "bump lean version"
- "rebuild the docker image"
- "smoke-test the image locally"
- "verify the GHCR pull works"
- "the docker CI failed"
- "is the docker image up to date?"
Canonical files
| Path | Purpose |
|---|---|
Dockerfile |
Multi-stage build, LEAN_VERSION build arg, single /opt/venv, non-root qagent user |
.dockerignore |
Mirrors .gitignore; re-includes MyProjects/ElectionIndustryBeta/ as the shipped demo |
.github/workflows/docker.yml |
Build on PR, push :latest + :sha-X on main, push :vX.Y.Z on tag |
docs/docker.md |
User-facing docs (quickstart, mounted dev, credentials, bumping LEAN) |
Task 1: Bump LEAN_VERSION
# Confirm current pin
grep '^ARG LEAN_VERSION=' Dockerfile
# Edit Dockerfile, change the default in the top-level ARG.
# Or build with --build-arg without editing.
# Build with the new version
docker build --build-arg LEAN_VERSION=<X.Y.Z> -t q-agent:dev .
# Run the full smoke suite (see Task 2)
After verifying locally, commit the Dockerfile change on a feature branch
and open a PR; main is branch-protected.
Task 2: Build + smoke-test locally
docker build -t q-agent:dev .
Then run every assertion (these mirror .github/workflows/docker.yml's
smoke-test stage):
docker run --rm q-agent:dev lean --help | head -5
docker run --rm q-agent:dev python -c \
"import ccxt, pandas, numpy, yfinance, tenacity, tqdm, dotenv, requests; print('OK')"
docker run --rm q-agent:dev python -c "import marimo; print(marimo.__version__)"
docker run --rm q-agent:dev pytest -m "not integration" \
--ignore=tests/hygiene -p no:cacheprovider -q
docker run --rm q-agent:dev test -d /workspace/MyProjects/ElectionIndustryBeta
docker run --rm -v "$(pwd):/workspace" q-agent:dev bash -lc 'ls MyProjects | head -5'
docker history q-agent:dev | grep -iE 'lean\.json|\.env|credentials|\.key' \
&& echo "FAIL: secrets in layers" || echo "OK: no secrets in history"
docker images q-agent:dev --format '{{.Size}}'
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.
- 2mo ago First seen · 234 lines · 50 tokens per session scan A 65fc3b3a3707
docker-workflow is a skill published in the GitHub repository WolfpackOfOne/Q-agent (5 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 2,266 once invoked, about $0.0002 per session on Opus 5.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
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
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-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…
CI/CD Pipeline Advanced
Expert-level CI/CD pipeline skill for test automation. Covers GitHub Actions, Jenkins, GitLab CI, Azure DevOps, parallel execution, matrix strategies, caching, artifact management, and deployment gates.
test-environments
Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment,"…