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/microsoft/hve-core/hve-buildernpx skills add microsoft/hve-core --skill hve-buildergit clone --depth 1 https://github.com/microsoft/hve-coreWrote 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/microsoft/hve-core/hve-builder)<a href="https://agentmods.dev/skills/microsoft/hve-core/hve-builder"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/hve-builder.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 | $0.00027 | $0.02263 |
| Opus 5 | $0.00014 | $0.01131 |
| Sonnet 5 | $0.00005 | $0.00453 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
hve-builder 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE Builder Skill
Role: lifecycle lead for Copilot instruction artifacts. Goal: create, improve, refactor, replace, review, or validate prompts, instruction files, agents, subagents, and skills through one evidence-backed workflow.
Read references/workflow-contract.md first. It owns mode routing, stage gates, model selection, iteration rules, and overall outcomes. Apply references/requirements-catalog.md as the quality standard, references/artifact-types.md for architecture and load timing, references/review-rubric.md for static verdicts, references/stage-dispatch.md for generic lifecycle-stage dispatches and the rpi-research bridge, and references/extending-hve-builder.md for host extensions. The hve-builder-tester skill is the sole behavior-testing entrypoint for Major mutations and behavior-bearing review targets.
Goal
Deliver the requested artifact set or evidence report with the narrowest necessary write authority. A passing route has an applicable behavior-gate result, required static verdicts, passing host validation when required, and no unmet acceptance criteria. A read-only run changes only its evidence files.
Modes
Use create, improve, refactor, replace, review, or validate as defined in references/workflow-contract.md. Infer the narrowest mode when the request is clear. Ask only when plausible modes would grant materially different write authority.
Flow
Follow the stage order, gates, classification, validation, and outcome resolver in references/workflow-contract.md. Apply these routing boundaries throughout that lifecycle:
- Intake may classify caller-provided facts, known targets, and already-supplied extension metadata without research.
- Activate
rpi-researchthrough references/stage-dispatch.md for every HVE Builder-initiated codebase exploration and every decision-critical internal, external, or hybrid research activity. - Keep bounded reads of already-known target files and supplied canonical references within baseline review, authoring, static review, and validation. They are lifecycle-stage work, not exploration.
- Apply the bridge return and unavailable-entrypoint behavior from references/stage-dispatch.md, then resolve the stage through the workflow contract. Do not substitute a local research route.
What ships with it
6 files 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.
- 4d ago First seen · 99 lines · 27 tokens per session scan A e4dd0462fad8
hve-builder is a skill published in the GitHub repository microsoft/hve-core (1,426 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 2,263 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…