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/boldblackai/harness/analyze-imagenpx skills add boldblackai/harness --skill analyze-imagegit clone --depth 1 https://github.com/boldblackai/harnessWrote 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/boldblackai/harness/analyze-image)<a href="https://agentmods.dev/skills/boldblackai/harness/analyze-image"><img src="https://agentmods.dev/badge/skills/boldblackai/harness/analyze-image.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.00119 | $0.00819 |
| Opus 5 | $0.00060 | $0.00409 |
| Sonnet 5 | $0.00024 | $0.00164 |
| Haiku 4.5 | $0.00012 | $0.00082 |
Grade A, and why
analyze-image 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 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.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Image Size
Produces a three-part breakdown of the harness Docker image:
- All available tags and their sizes
- Per-layer contribution (from
docker history) - Efficiency and waste report (from
dive --ci)
Step 1: Determine target image
Default to ghcr.io/boldblackai/harness:latest unless the user specifies a different tag.
Step 2: List all harness image tags
docker images ghcr.io/boldblackai/harness --format "table {{.Tag}}\t{{.Size}}\t{{.CreatedAt}}"
Step 3: Per-layer breakdown
docker history <image> --no-trunc --format "table {{.Size}}\t{{.CreatedBy}}"
Most layers will be 0B (metadata). Focus the summary on layers with non-zero size. Translate the raw CREATED BY commands into human-readable descriptions:
| Raw command fragment | Human label |
|---|---|
apt-get install / NodeSource setup |
"System packages + Node.js" |
corepack / pnpm install -g |
"pnpm + agent packages" |
COPY / chmod / mkdir |
"Config files / entrypoint" |
| Base layer (no command) | "Base OS (debian:stable-slim)" |
Step 4: Base image size
Read Dockerfile to find the FROM line and extract the base image reference (including the pinned digest). Pull it if needed and inspect its uncompressed size:
docker pull <base-image-with-digest> 2>/dev/null
docker inspect <base-image-with-digest> --format '{{.Size}}' | awk '{printf "%.0f MB\n", $1/1024/1024}'
Step 5: Dive efficiency analysis
docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
wagoodman/dive:latest --ci <image>
This outputs:
- Overall efficiency percentage
- Total wasted bytes
- A ranked list of inefficient files (files duplicated across layers)
Step 6: Report
Present the results as a unified report:
## Image size analysis: <image>
### Tags
<table of tag / size / created>
### Layer breakdown
| Size | Layer |
|--------|------------------------------|
| 100 MB | Base OS (debian:stable-slim) |
| 249 MB | System packages + Node.js |
| 429 MB | pnpm + agent packages |
| ~1 MB | Config files / entrypoint |
Base image accounts for X MB of the Y MB total.
### Efficiency (dive)
- Efficiency: XX%
- Wasted: XX MB
Top waste sources:
| Wasted | File | Likely cause |
|--------|------|--------------|
...
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 · 95 lines · 119 tokens per session scan A c1c127fdb40a
analyze-image is a skill published in the GitHub repository boldblackai/harness (10 stars, last pushed 3d ago), licensed MIT. It adds 119 tokens to every session and 819 once invoked, about $0.0006 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.