test-boost-module

A live integration test for a Harbor Boost module, sending a real prompt through a local language model and checking the result.

In plain words
What is it for?
Use it to verify, debug, or quality-check a Boost module when Harbor services and a test model are available.
Why use it?
It shows whether a module changes model behavior in the running system, rather than only passing isolated code tests.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/av/harbor/test-boost-module
Any agent
npx skills add av/harbor --skill test-boost-module
Clone the repo
git clone --depth 1 https://github.com/av/harbor

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash c1f601d97c8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 "
.agents/skills/test-boost-module/SKILL.md · 132 lines

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

  • llamacpp running (harbor up llamacpp)
  • boost running (harbor up boost)
  • pi installed 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
  • --model is the base llamacpp model (no module prefix)
  • -p makes pi print-and-exit (non-interactive)
  • --no-tools disables tool use for a clean completion
  • --no-session keeps 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

Read the full file on GitHub · 132 lines

Changes

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.

  1. yesterday First seen · 132 lines · 61 tokens per session scan A c1f601d97c8e

Subscribe to this mod's changes

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.

Related

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.

kurtosis-tech/kurtosis · 56 tokens

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.

kurtosis-tech/kurtosis · 51 tokens

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.

kurtosis-tech/kurtosis · 78 tokens

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.

kurtosis-tech/kurtosis · 50 tokens

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.

kurtosis-tech/kurtosis · 45 tokens

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.

kurtosis-tech/kurtosis · 52 tokens