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 skills/pigfoot/claude-code-hubs/github-actions-container-buildnpx skills add pigfoot/claude-code-hubs --skill github-actions-container-buildgit clone --depth 1 https://github.com/pigfoot/claude-code-hubsWrote 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/pigfoot/claude-code-hubs/github-actions-container-build)<a href="https://agentmods.dev/skills/pigfoot/claude-code-hubs/github-actions-container-build"><img src="https://agentmods.dev/badge/skills/pigfoot/claude-code-hubs/github-actions-container-build.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.00056 | $0.02513 |
| Opus 5 | $0.00028 | $0.01256 |
| Sonnet 5 | $0.00011 | $0.00503 |
| Haiku 4.5 | $0.00006 | $0.00251 |
Grade B, and why
github-actions-container-build scanned grade B with 2 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 4d 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 rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo cp -f podman-linux-${PODMAN_ARCH}/usr/local/bin/* /usr/bin/ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL -o /tmp/podman-linux-${PODMAN_ARCH}.tar.gz \ How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Container Build
Build multi-architecture container images in GitHub Actions using Podman and native ARM64 runners.
Core Principles
Choose Your Workflow
CRITICAL: Ask these questions before generating any workflow.
Question 1: Is your GitHub repository public?
- Yes → Use
github-actions-workflow-matrix-build.yml(free standard ARM64 runners, 10-50x faster) - No → Go to Question 2
Question 2: Do you have GitHub Team/Enterprise + willing to pay for ARM64 builds?
- Yes → Use ARM64 larger runners (custom setup required, paid per minute)
- No → Use
github-actions-workflow-qemu.yml(free QEMU emulation, slower but works on free tier)
1. Push-by-Digest (2025 Best Practice - Default)
Matrix builds use push-by-digest pattern:
- Images pushed by digest without intermediate
:amd64/:arm64tags - Only tiny digest files (~70 bytes) transfer as artifacts
- Registry stays clean (no tag clutter)
- Same debug experience with
--platformflag
# Build job
- name: Push by digest
run: |
podman push \
--digestfile /tmp/digest \
localhost/build:${{ matrix.arch }} \
docker://${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
# Merge job
- name: Create manifest from digests
run: |
podman manifest create "$IMAGE:latest"
podman manifest add "$IMAGE:latest" "docker://$IMAGE@${AMD64_DIGEST}"
podman manifest add "$IMAGE:latest" "docker://$IMAGE@${ARM64_DIGEST}"
podman manifest push --all "$IMAGE:latest" "docker://$IMAGE:latest"
Debug specific architecture:
podman pull --platform linux/arm64 ghcr.io/OWNER/REPO:latest
2. Matrix Builds (Public Repos)
For public repositories - use GitHub-hosted standard ARM64 runners:
- 10-50x faster builds (native vs. emulation)
- Better reliability and accuracy
- Lower CI costs
- Completely free for public repos
- Not available for private repos
strategy:
matrix:
include:
- arch: amd64
runner: ubuntu-24.04
- arch: arm64
runner: ubuntu-24.04-arm # Standard ARM64 runner (public repos only)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 324 lines · 56 tokens per session scan B 5a447d734b5e
github-actions-container-build is a skill published in the GitHub repository pigfoot/claude-code-hubs (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 2,513 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). 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…
konflux-build
Create a manual Konflux build from a PR with configurable image expiry (default 30 days).
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-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.
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.