HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.
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 microsoft/hve-core --skill hve-builder-testergit 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-tester)<a href="https://agentmods.dev/skills/microsoft/hve-core/hve-builder-tester"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/hve-builder-tester.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.01901 |
| Opus 5 | $0.00029 | $0.00950 |
| Sonnet 5 | $0.00012 | $0.00380 |
| Haiku 4.5 | $0.00006 | $0.00190 |
Grade A, and why
hve-builder-tester 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 yesterday.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE Builder Tester Skill
Goal
Exercise a prompt, instruction, agent, subagent, or skill once through representative black-box scenarios and produce a durable report that states exactly what the evidence supports. The report is evidence for the caller; this skill never edits the target or prescribes a retest.
This skill owns scope, scenario design, fidelity, sandbox state, execution evidence, independent grading, reporting, and cleanup. Read references/test-methodology.md for black-box design, fidelity, and containment decisions, references/stage-dispatch.md for independent grading, and references/report-format.md for the durable report.
Use Cases
- Run the final behavior gate for HVE Builder's frozen Major change or behavior-bearing review target.
- Test an existing artifact directly without editing it, using its documented inputs and expected outcomes.
- Check a connected artifact set for handoff behavior, or assess whether required behavior survives instruction cleanup, relocation, or replacement.
Flow
- Resolve targets, types, purpose, requirements, profile, requested fidelity, isolation and together sets, sandbox root, candidate revision, and report path. If no runtime behavior exists, write a supported skip report and return.
- Select fidelity through the methodology preconditions. Default to simulation. When requested native execution is unsupported or unsafe, use simulation only with caller acceptance; otherwise return Deferred with the rerun condition.
- Capture pre-run workspace state and create a unique sandbox containing
run-state.md. Record the candidate revision, profile and model, fidelity, groupings, purpose, requirements, containment controls, and requirement map. - Design the smallest black-box scenario set that covers the documented contract. Assign stable scenario IDs, map requirements to observable outcomes, record intentional gaps, perform the black-box self-check, and write
test-design.md. If credible design is unavailable, return Deferred without execution. - Execute every scenario once. For simulation, dispatch
HVE Artifact Testerwith the resolved model bound through the host's model-selection parameter. Record binding evidence under the methodology's Profile Selection rules. For native fidelity, invoke the registered target directly when containment permits it. Never silently substitute fidelity or fabricate evidence after a failed execution. - Write
test-log.mdwith the returned trace, observed versus simulated or emulated actions, fidelity, candidate revision, containment checks, workspace delta, and untested behavior. - Dispatch one independent grader at the higher of Medium and the target profile. Give it the finalized design and log, targets, purpose, requirements, catalog, and rubric. Validate its bounded Pass, Revise, or Blocked return and write
test-review.md. - Write the durable report outside the sandbox, preserving the scenario inputs, requirement map, decisive trace evidence, and grading rationale needed to assess the verdict without transient files. Then clean up unless retention was requested. Return the report without revising the target.
What ships with it
3 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.
- yesterday Changed · -15 lines · +28 tokens per session bae071cfbcca
- 8d ago First seen · 126 lines · 30 tokens per session scan A 5d3c6a24dc9f
hve-builder-tester is a skill published in the GitHub repository microsoft/hve-core (1,436 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,901 once invoked, about $0.0003 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.