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/harbor-framework/harbor/harbor-execnpx skills add harbor-framework/harbor --skill harbor-execgit clone --depth 1 https://github.com/harbor-framework/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.00071 | $0.00779 |
| Opus 5 | $0.00036 | $0.00390 |
| Sonnet 5 | $0.00014 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
harbor-exec 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- harbor-exec — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harbor Exec
Overview
Use this skill to operate Harbor's harbor exec command. Treat harbor exec as agentic map-reduce: it turns loose inputs into Harbor tasks, runs Harbor jobs over those tasks, and optionally aggregates the results.
First Checks
Assume the user is running an installed Harbor CLI. Check the installed command surface before making claims:
harbor --version
harbor exec --help
Require Harbor >=0.17.1 for harbor exec. If harbor --version reports an older version, ask the user to upgrade before continuing.
Use --print-config when debugging config resolution, inferred artifacts, task/job directories, or defaults. Do not treat it as a substitute for showing the final launch command.
If the installed harbor command is not available, ask the user how they installed Harbor before guessing a command path.
Run Parameter Questions
Before running a Harbor Exec job, ask the user to confirm any unspecified run parameters:
- Inputs: exact paths/globs and whether to
--scanor--no-scan. - Artifact contract: output file paths the agent must write.
- Artifact schemas: required JSON or structured schema for each artifact.
- Environment provider: recommend cloud sandboxing over local
docker; suggestmodal,daytona, ore2b. - Agent and model for the map step.
- Concurrency count.
- Whether to include a reduce step, and if so which reduce agent and model to use.
- Final command: show the exact launch command before running it.
Usage Workflow
Prefer flags for one-off runs and --config for repeatable or map-reduce workflows.
Make artifacts explicit when correctness depends on generated files:
harbor exec -p ./input -i "Write /app/answer.json" -f /app/answer.json
Prefer explicit artifacts over auto-inferred artifacts. Auto-inference only reads inline instructions, not instruction files.
Do not persist compiled tasks by default. Omit --tasks-dir unless the user wants to inspect or reuse compiled tasks; when omitted, compiled tasks are ephemeral and cleaned up after execution.
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.
- 3d ago First seen · 77 lines · 71 tokens per session scan A 7a74b4a046bb
harbor-exec is a skill published in the GitHub repository harbor-framework/harbor (4,854 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 779 once invoked, about $0.0004 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-30.
Other skills, from other repositories
tracely
Instrument AI agents with Tracely and turn their production traces into CI gates. Use when the user mentions Tracely, tracely-ai, tracelysdk, the tracely CLI, or asks to trace/observe an AI agent, add LLM evaluators or LLM-as-a-judge columns, debug why a trace or conversation isn't showing up, wire agent regression…
new-tool
Add a new tool to Waku the right way — schema, safe execution, deterministic eval, honest output. Use when adding or modifying agent tools or when the user asks for a new capability.
benchflow-traj-upload
Find a local Claude Code or Codex session, open the BenchFlow trajectory viewer, and submit it after the user reviews it. Use this skill whenever someone pastes a BenchFlow eval prize line, wants to submit / share / contribute / upload a trajectory, set up traj upload, view a session, or pick a session to send. Also…
benchflow-traj-upload-ops
Operate, test, troubleshoot, and explain bench traj upload for public or trusted-direct trajectory contributions, including interactive and fully specified commands, dry runs, input validation, local secret masking, trajectory reports and previews, manifest metadata, upload progress, idempotency, and production…
skillforge
Use when creating, improving, finding, or auditing agent skills - the user says 'create a skill', 'do I have a skill for X', 'improve the X skill', 'which skill should I use', asks whether a skill exists for a task, or wants to validate, test, evaluate, package, or health-check skills. Also use for skill ecosystem…
mastra-smoke-test
Smoke test Mastra projects locally or deploy to staging/production. Tests Studio UI, agents, tools, workflows, traces, memory, and more. Supports both local development and cloud deployments.