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/bugbashnpx skills add av/harbor --skill bugbashgit 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.00058 | $0.01276 |
| Opus 5 | $0.00029 | $0.00638 |
| Sonnet 5 | $0.00012 | $0.00255 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
bugbash 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Repro Steps:** Exact commands run, API requests made (e.g., `curl` commands), or code executed. How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bugbash (General Software)
Systematically explore a software project, find issues, and produce a report with full reproduction evidence for every finding. This skill applies to CLIs, APIs, Backends, Libraries, and other non-web interfaces.
Setup
Identify the Target (e.g., a CLI binary, an API base URL, a Python package).
| Parameter | Default | Example override |
|---|---|---|
| Target | (required) | ./my-cli, http://localhost:8080, import mylib |
| Output directory | /tmp/dogfood-output/ |
Output directory: ./qa-reports |
| Scope | Full project | Focus on the auth middleware |
Workflow
1. Initialize Set up output dirs, report file, build/start the software
2. Orient Discover surface area (help menus, API schemas, exported functions)
3. Explore Systematically test features, inputs, and edge cases
4. Document Record exact inputs, outputs, and logs for each issue
5. Wrap up Update summary counts, finalize report
1. Initialize
mkdir -p {OUTPUT_DIR}/logs {OUTPUT_DIR}/evidence
Create a report.md in the output directory and fill in the header fields. Include:
- Target
- Date
- Environment Details (OS, language version)
- Summary Counts (Critical, High, Medium, Low)
If the software needs to be built or started (e.g., npm run build, docker-compose up, cargo build), do that now. Keep track of the startup logs and run servers in the background if necessary (e.g., using & and redirecting output).
2. Orient
Map out the surface area of the software before testing.
- For CLIs: Run
{TARGET} --help, list subcommands, check environment variable configurations. - For APIs: Fetch OpenAPI/Swagger specs, list route definitions in code, or run a schema discovery tool.
- For Libraries: Inspect exported modules, classes, and public methods.
Save this initial mapping to {OUTPUT_DIR}/surface-area.txt.
3. Explore
Work through the surface area systematically.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 101 lines · 58 tokens per session scan A a587c2fa6c2c
bugbash is a skill published in the GitHub repository av/harbor (3,198 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,276 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.