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/test-boost-modulenpx skills add av/harbor --skill test-boost-modulegit 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.00061 | $0.01383 |
| Opus 5 | $0.00030 | $0.00691 |
| Sonnet 5 | $0.00012 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
test-boost-module 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.
curl -s -H "Authorization: Bearer sk-boost" http://localhost:$(docker port harbor.boost 8000/tcp | head -1 | cut -d: -f2)/v1/models | python3 -c " How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Boost Module
Send a real prompt through a running Boost module via harbor launch + pi and
validate the output yourself. This is a live integration test, not a unit test.
Prerequisites
llamacpprunning (harbor up llamacpp)boostrunning (harbor up boost)piinstalled on the host
If services aren't running, start them. Wait for health checks before proceeding.
Picking a Test Model
Use a small-to-mid model already available in llamacpp. Check what's loaded:
curl -s -H "Authorization: Bearer sk-boost" http://localhost:$(docker port harbor.boost 8000/tcp | head -1 | cut -d: -f2)/v1/models | python3 -c "
import sys, json
for m in json.load(sys.stdin).get('data', []):
if m.get('status', {}).get('value') == 'loaded':
print(f\" LOADED {m['id']}\")
else:
print(f\" avail {m['id']}\")
" 2>/dev/null
Good defaults (if available): unsloth/Qwen3.6-35B-A3B-GGUF:Q4_K_XL,
unsloth/Qwen3.5-4B-GGUF:Q4_K_M, or any loaded non-embedding model.
Strip the module prefix from the model ID when passing to --model.
The Command
harbor launch --workflow <module_name> --model "<base_model_id>" pi \
-p --no-tools --no-session "<prompt>"
--workflow <module_name>routes through Boost with that module active--modelis the base llamacpp model (no module prefix)-pmakes pi print-and-exit (non-interactive)--no-toolsdisables tool use for a clean completion--no-sessionkeeps it ephemeral
Argument order matters
Launch options (--workflow, --model, --backend) go before pi.
Pi options (-p, --no-tools) and the prompt go after pi.
Choosing the Right Prompt
The prompt should make the module's effect obvious in the output. Pick a prompt that produces clearly different output with vs. without the module.
Prompt strategies by module type
| Module type | Good prompt | What to look for |
|---|---|---|
| Style/compression (caveman, ponytail) | "Explain the theory of relativity in detail" | Terse fragments or minimal-build guidance vs. normal prose |
| Reasoning chain (g1, mcts, ponder) | "What is 27 * 43?" or a logic puzzle | Visible thinking steps, multi-pass reasoning |
| Research/retrieval (quickhop, deephop) | "What are the latest developments in fusion energy?" | Citations, search steps, retrieved context |
| Output transform (eli5, klmbr, rcn) | "Explain quantum entanglement" | Simplified language, restructured output |
| Guard/check (autocheck, diffscope) | A coding deliverable with explicit file scope | Post-answer self-check or scope warnings |
| Prompt injection (dnd, dot, nbs) | Any general question | System prompt artifacts, altered persona |
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 · 132 lines · 61 tokens per session scan A c1f601d97c8e
test-boost-module is a skill published in the GitHub repository av/harbor (3,198 stars, last pushed 2d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,383 once invoked, about $0.0003 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.