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-artifact-authoringgit 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-artifact-authoring)<a href="https://agentmods.dev/skills/microsoft/hve-core/hve-artifact-authoring"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/hve-artifact-authoring/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/microsoft/hve-core/hve-artifact-authoring"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/hve-artifact-authoring.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01354 |
| Opus 5 | $0.00027 | $0.00677 |
| Sonnet 5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
hve-artifact-authoring 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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE Artifact Authoring
Goal
Create agents, prompts, instructions, and skills that follow HVE Core's current authoring,
distribution, documentation, and validation contracts. Use the hve-builder skill when the work
requires lifecycle-managed authoring, independent review, behavior testing, or host validation.
Artifact Selection
Choose each artifact from its responsibility and activation model.
| Artifact | Responsibility | Activation |
|---|---|---|
Prompt (.prompt.md) |
Parameterized user entry point | Slash invocation |
Agent (.agent.md) |
User-selected workflow or isolated subagent work | Agent picker or parent dispatch |
Instruction (.instructions.md) |
Conventions applied to matching paths | applyTo glob |
Skill (SKILL.md) |
Reusable workflow, domain knowledge, references, or utilities | Semantic match or slash invocation |
Keep reusable behavior in a skill. Add a thin prompt or agent only when it provides a distinct entry point. Delegate isolated work only when the dispatch cost is justified.
Flow
- Identify the artifact responsibility, activation path, package ID, targets, requirements, success criteria, constraints, and stop rules.
- Search for an existing artifact that can be reused or extended before creating another one.
- Select the matching bundled starter asset when the caller wants a new artifact:
assets/agent-template.mdassets/prompt-template.mdassets/instruction-template.mdassets/skill-template.md
- Replace every placeholder and remove unused optional fields. Do not copy a starter unchanged.
- Write the artifact outcome-first. State the goal, scored success criteria, constraints, stop rules, workflow, and response contract. Add delegation and tracking only when needed.
- Synchronize current distribution and documentation projections.
- Run the checks owned by the changed artifact type and record evidence.
What ships with it
5 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.
- 3d ago First seen · 145 lines · 54 tokens per session scan A 33b3f55fb0ea
hve-artifact-authoring is a skill published in the GitHub repository microsoft/hve-core (1,437 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,354 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-09-05.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…