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/zli12321/lhtb/publishnpx skills add zli12321/LHTB --skill publishgit clone --depth 1 https://github.com/zli12321/LHTBWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zli12321/lhtb/publish)<a href="https://agentmods.dev/skills/zli12321/lhtb/publish"><img src="https://agentmods.dev/badge/skills/zli12321/lhtb/publish.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00865 |
| Opus 5 | $0.00017 | $0.00432 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
publish 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 6d 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.
This is a copy
95% identical to publish — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Help the user publish a Harbor task or dataset to the registry. Walk them through each step, checking prerequisites and confirming before running publish commands.
All commands use uvx harbor so the user does not need to install the CLI globally.
Prerequisites
-
Auth: Ensure the user is logged in by running
uvx harbor auth status. If not logged in, prompt them to runuvx harbor auth login. -
Task identifiers: All tasks must have a
[task]section in theirtask.tomlwith a name like<org>/<name>. If missing, run:uvx harbor task update "<path/to/task>" --org "<org>"To update all tasks in a directory:
uvx harbor task update "<path/to/tasks>" --org "<org>" --scan
Publishing a task
uvx harbor publish "<path/to/task>"
Publish multiple tasks or all tasks in a directory:
uvx harbor publish "<path/to/task-a>" "<path/to/task-b>"
uvx harbor publish "<path/to/tasks>"
Publishing a dataset
1. Initialize the dataset manifest (if no dataset.toml exists)
uvx harbor dataset init "<org>/<dataset>" \
--description "<description>" \
--author "Jane Doe <[email protected]>"
Add --with-metric if the user needs a custom metric script. If omitted, the dataset uses the default metric (average reward across tasks, with missing values treated as 0).
Auto-add behavior: If dataset init is run in a directory that already contains tasks, those tasks are automatically added to the manifest. After init, ask the user if they want to add additional tasks — either from the Harbor registry or from other local folders.
2. Add additional tasks and files (optional)
cd "<path/to/dataset>"
uvx harbor add "<path/to/task-a>" "<path/to/task-b>" # local tasks from elsewhere
uvx harbor add "<path/to/folder>" --scan # all tasks in another folder
uvx harbor add org/task-name # published tasks from registry
uvx harbor add org/dataset-name # all tasks from a published dataset
uvx harbor add metric.py # metric file (same dir as dataset.toml)
uvx harbor remove "<org>/<task-name>" # remove a task
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.
- 6d ago First seen · 98 lines · 35 tokens per session scan A ae59c24dc61a
publish is a skill published in the GitHub repository zli12321/LHTB (697 stars, last pushed 9d ago), licensed Apache-2.0. It adds 35 tokens to every session and 865 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to publish, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
upload-parity-experiments
Create or reuse Hugging Face dataset PRs for harborframework/parity-experiments and upload Harbor parity/oracle result folders efficiently with sparse checkout, raw git pushes, and Git LFS.
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.