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 agentmods add skills/microsoft/hve-core/hve-core-installernpx skills add microsoft/hve-core --skill hve-core-installergit 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-core-installer)<a href="https://agentmods.dev/skills/microsoft/hve-core/hve-core-installer"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/hve-core-installer.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.00028 | $0.04086 |
| Opus 5 | $0.00014 | $0.02043 |
| Sonnet 5 | $0.00006 | $0.00817 |
| Haiku 4.5 | $0.00003 | $0.00409 |
Grade C, and why
hve-core-installer scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
| 1 (Peer Clone) | `rm -rf ../hve-core` | How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE-Core Installer Skill
Decision-driven installer for HVE-Core with environment detection, 6 clone-based installation methods, extension quick-install, validation, MCP configuration, and selective component installation workflows.
Role Definition
Operate as two collaborating personas:
- The Installer persona detects the environment, guides method selection, and executes installation steps
- The Validator persona verifies installation success by checking paths, settings, and agent accessibility
The Installer persona handles all detection and execution. After installation completes, switch to the Validator persona to verify success before reporting completion.
Re-run Behavior: Running the installer again validates an existing installation or offers upgrade. Safe to re-run anytime.
Required Phases
| Phase | Name | Purpose |
|---|---|---|
| 1 | Environment Detection | Obtain consent and detect user's environment |
| 2 | Installation Path Selection | Choose between Extension (quick) or Clone-based installation |
| 3 | Environment Detection & Decision Matrix | For clone path: detect environment and recommend method |
| 4 | Installation Methods | Execute the selected installation method |
| 5 | Validation | Verify installation success and configure settings |
| 6 | Post-Installation Setup | Configure gitignore and present MCP guidance |
| 7 | Component Installation | Optional: copy selected components for local use (clone-based only) |
Flow paths:
- Extension path: Phase 1 → Phase 2 → Phase 6 → Complete
- Clone-based path: Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 5 → Phase 6 → Phase 7 → Complete
What ships with it
28 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.
- examples/README.md 3.3 KB
- references/component-installation.md 15 KB
- references/installation-methods.md 13 KB
- references/post-installation-setup.md 8.1 KB
- scripts/collision-detection.ps1 1.6 KB runs code
- scripts/collision-detection.sh 1006 B runs code
- scripts/component-copy.ps1 18 KB runs code
- scripts/component-copy.sh 16 KB runs code
- scripts/detect-environment.ps1 1.5 KB runs code
- scripts/detect-environment.sh 1.3 KB runs code
- scripts/eject.ps1 3.2 KB runs code
- scripts/eject.sh 2.0 KB runs code
- scripts/file-status-check.ps1 2.6 KB runs code
- scripts/file-status-check.sh 2.2 KB runs code
- scripts/upgrade-detection.ps1 2.5 KB runs code
- scripts/upgrade-detection.sh 2.1 KB runs code
- scripts/validate-extension.ps1 1.3 KB runs code
- scripts/validate-extension.sh 1.1 KB runs code
- scripts/validate-installation.ps1 2.1 KB runs code
- scripts/validate-installation.sh 1.9 KB runs code
- tests/collision-detection.Tests.ps1 8.1 KB runs code
- tests/component-copy.Tests.ps1 50 KB runs code
- tests/detect-environment.Tests.ps1 3.8 KB runs code
- tests/eject.Tests.ps1 11 KB runs code
- tests/file-status-check.Tests.ps1 8.4 KB runs code
- tests/upgrade-detection.Tests.ps1 9.8 KB runs code
- tests/validate-extension.Tests.ps1 4.3 KB runs code
- tests/validate-installation.Tests.ps1 9.0 KB runs code
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 8b15bb518616
- 6d ago First seen · 492 lines · 28 tokens per session scan C 0c0bd688144d
hve-core-installer is a skill published in the GitHub repository microsoft/hve-core (1,436 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 4,086 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…