Borrowing it
Nothing to install: this file belongs to divinevideo/divine-mobile. 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/divinevideo/divine-mobile/main/.agents/skills/docker-buildx-stale-rust-binary/SKILL.mdgit clone --depth 1 https://github.com/divinevideo/divine-mobileWrote 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/divinevideo/divine-mobile/docker-buildx-stale-rust-binary)<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/docker-buildx-stale-rust-binary"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/docker-buildx-stale-rust-binary.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.00115 | $0.00825 |
| Opus 5 | $0.00057 | $0.00413 |
| Sonnet 5 | $0.00023 | $0.00165 |
| Haiku 4.5 | $0.00012 | $0.00082 |
Grade C, and why
docker-buildx-stale-rust-binary scanned grade C 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 7d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
RUN cargo build --release && rm -rf src crates How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Buildx Stale Rust Binary Cache
Problem
Docker buildx may serve stale compiled Rust binaries from layer cache even when source
files have changed. The image gets a new tag and pushes successfully, but contains the
old compiled binary. This is especially common with cross-platform builds
(--platform linux/amd64 on ARM Macs).
Context / Trigger Conditions
- Dockerfile uses multi-stage pattern: copy Cargo.toml → build deps → copy source → build
- Using
docker buildx build --pushwith--platform linux/amd64 - Code changes verified locally (tests pass) but production shows old behavior
- Image digest from cached build differs from
--no-cachebuild - Adding a simple response header in code and it doesn't appear in production
Solution
Always use --no-cache when deploying code changes:
# WRONG — may use cached compilation layer with old code
docker buildx build --platform linux/amd64 --target api \
-t registry/image:tag --push .
# CORRECT — forces full recompilation
docker buildx build --platform linux/amd64 --target api \
--no-cache -t registry/image:tag --push .
Verification
Compare image digests between cached and no-cache builds:
# Build with cache
docker buildx build --platform linux/amd64 --target api \
-t registry/image:cached --push . 2>&1 | grep "pushing manifest"
# Note the sha256 digest
# Build without cache
docker buildx build --platform linux/amd64 --target api \
--no-cache -t registry/image:nocache --push . 2>&1 | grep "pushing manifest"
# Note the sha256 digest
# If digests differ, the cached build had stale code
Example
Typical Dockerfile pattern vulnerable to this:
# Layer 1: Copy manifests (cached if Cargo.toml unchanged)
COPY Cargo.toml Cargo.lock ./
COPY crates/*/Cargo.toml crates/
# Layer 2: Build dependencies (cached — this is the good cache)
RUN cargo build --release && rm -rf src crates
# Layer 3: Copy actual source (SHOULD invalidate on source change)
COPY crates crates
COPY bin bin
# Layer 4: Rebuild with actual source
RUN touch crates/*/src/lib.rs && cargo build --release
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.
- 7d ago First seen · 93 lines · 115 tokens per session scan C db229c3f500d
docker-buildx-stale-rust-binary is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 115 tokens to every session and 825 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
meta-home-it-rescue
Use this meta-skill instead of answering directly when the user needs help with home, small-team, laptop, browser, printer, Docker, Git, network, UI, or deployment troubleshooting that benefits from multi-skill orchestration across symptom intake, environment capture, web lookup, and repair planning.
debugging-local-replay
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy…
docker-debug
Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.