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/av/harbor/releasenpx skills add av/harbor --skill releasegit clone --depth 1 https://github.com/av/harborWhat 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.00098 | $0.01847 |
| Opus 5 | $0.00049 | $0.00924 |
| Sonnet 5 | $0.00020 | $0.00369 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
release 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import urllib.parse How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harbor Release Procedure
Releasing Harbor is a sequential pipeline: bump the version constant, run codegen (which propagates the version across the monorepo and syncs docs to the wiki), research what changed, update the README News section, run the same local lint gate used by CI, commit, push, and open a pre-filled GitHub release form.
Pre-flight
Before starting, verify two things:
- Clean working tree —
git statusshould show no uncommitted changes. The codegen step touches many files; starting dirty makes the release commit noisy. - Wiki repo exists —
release.shpushes docs to../harbor.wiki. If the directory doesn't exist, the docs push will fail. Clone it first if missing:git clone https://github.com/av/harbor.wiki.git ../harbor.wiki
Step 1 — Bump Version
Open .scripts/seed.ts and change the VERSION constant (line ~9):
const VERSION = "X.Y.Z";
Bump patch by default (e.g. 0.4.2 → 0.4.3). Bump minor or major only
when the user explicitly asks.
This constant is the single source of truth — the seed script propagates it to
pyproject.toml, package.json, harbor.sh, app/package.json,
app/src-tauri/tauri.conf.json, app/src-tauri/Cargo.toml, and
services/boost/pyproject.toml.
Step 2 — Run Codegen
bash .scripts/release.sh
Note: harbor dev only runs .scripts/*.ts Deno scripts, so release.sh must
be invoked directly with bash. The script:
- Seeds the version into all targets (
harbor dev seed,seed-cdi,seed-traefik) - Runs the human lint pass (
harbor dev lint) - Refreshes
app/src-tauri/Cargo.lockto match the bumpedCargo.toml(cargo update --workspace); ifcargois missing it warns — sync the lock manually before committing - Regenerates docs and pushes them to the wiki repo (
../harbor.wiki)
Wait for it to complete. Check the output for errors — especially the wiki push,
which can fail if there are merge conflicts in ../harbor.wiki.
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.
- yesterday First seen · 212 lines · 98 tokens per session scan A 659b39e0d2d5
release is a skill published in the GitHub repository av/harbor (3,198 stars, last pushed 2d ago), licensed Apache-2.0. It adds 98 tokens to every session and 1,847 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
docker-local-build
Build and test Kurtosis from source on local Docker. Compiles all components (engine, core, files-artifacts-expander), builds Docker images, installs the CLI, and restarts the engine. Use when developing Kurtosis and testing changes locally with Docker.
files-inspect
Inspect, download, upload, and debug Kurtosis file artifacts. View artifacts in an enclave, download them locally for inspection, upload local files, and troubleshoot file mounting issues. Use when services can't find expected files or configs are wrong.
k8s-dev-deploy
Build, push, and deploy Kurtosis dev images to a Kubernetes cluster without creating a release. Rebuilds engine, core, and files-artifacts-expander as multi-arch Docker images with a unique tag, pushes to the logged-in user's Docker Hub, and restarts the engine. Use when testing local code changes on a k8s cluster.
starlark-dev
Develop and debug Kurtosis Starlark packages. Create packages from scratch, understand the plan-based execution model, use print() debugging, handle future references, and test packages locally. Use when writing or troubleshooting .star files.
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.
enclave-inspect
Inspect and manage Kurtosis enclaves. List enclaves, view services and ports, examine file artifacts, dump enclave state for debugging, and clean up. Use when you need to understand what's running inside an enclave or export its state.