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 skills add pku-liang/hwe-bench --skill upload-parity-experimentsgit clone --depth 1 https://github.com/pku-liang/hwe-benchWrote 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/pku-liang/hwe-bench/upload-parity-experiments)<a href="https://agentmods.dev/skills/pku-liang/hwe-bench/upload-parity-experiments"><img src="https://agentmods.dev/badge/skills/pku-liang/hwe-bench/upload-parity-experiments/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/pku-liang/hwe-bench/upload-parity-experiments"><img src="https://agentmods.dev/badge/skills/pku-liang/hwe-bench/upload-parity-experiments.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.01644 |
| Opus 5 | $0.00024 | $0.00822 |
| Sonnet 5 | $0.00010 | $0.00329 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
upload-parity-experiments 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 10d 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
100% identical to upload-parity-experiments — 0 lines 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upload Parity Experiments
Use this skill to publish Harbor parity experiment outputs to the shared Hugging Face dataset and capture the resulting discussion URL for the adapter's parity_pr field.
Why This Skill Exists
hf upload-large-foldercan be slow or unreliable for large parity bundles because it pushes through the Hub API commit loop.- A normal git clone of
harborframework/parity-experimentsis too expensive because the dataset is very large. - Hugging Face dataset PR refs are different from GitHub PR refs and are easy to misuse.
- Files larger than 10 MiB must be Git LFS-tracked before pushing.
This skill avoids the full clone by fetching only the target PR ref with --depth 1 --filter=blob:none and checking out only the paths needed for the current adapter.
Prereqs
- Ensure Hugging Face authentication is available with discussion-write permission. Either a classic
writetoken or a fine-grained token with globaldiscussion.writeenabled at https://huggingface.co/settings/tokens. A read-only or narrowly-scoped token will causecreate_pr.pyto fail with HTTP 403. - Keep the target dataset fixed to
harborframework/parity-experimentsunless the user explicitly asks for another repo. - Accept any local upload source that already contains the final files the user wants to publish.
Preferred Workflow
- Create or reuse a dataset PR.
- Prepare a sparse local worktree for that PR ref.
- Copy the local parity results into the sparse checkout.
- Ensure every file larger than 10 MiB is Git LFS-tracked before committing.
- Push directly to the PR ref with raw
git push. - Share the discussion URL and record it as the adapter's
parity_pr.
For large parity bundles, prefer raw git over hf upload-large-folder. The raw git path is materially faster and more reliable because it avoids the API-side commit loop and does not require cloning the entire parity dataset.
1. Create Or Reuse A Dataset PR
If the user already has a parity PR number, reuse it.
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.
- 10d ago First seen · 176 lines · 49 tokens per session scan A 257567d704bf
upload-parity-experiments is a skill published in the GitHub repository pku-liang/hwe-bench (55 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,644 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to upload-parity-experiments, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.