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.
Borrowing it
Nothing to install: this file belongs to microsoft/hve-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/hve-core/main/.github/instructions/pull-request.instructions.mdgit 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/instructions/microsoft/hve-core/pull-request)<a href="https://agentmods.dev/instructions/microsoft/hve-core/pull-request"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/pull-request/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/instructions/microsoft/hve-core/pull-request"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/pull-request.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.00592 | $0.00592 |
| Opus 5.5 | $0.00237 | $0.00237 |
| Sonnet 5.5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
hve-core pull-request.instructions.md 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HVE Core Pull Request Conventions
Apply these repository-specific rules when the pull request skill prepares or updates a pull request for HVE Core.
Human-Only Checkboxes
Leave these items unchecked:
- HVE Builder review attestations
- AI artifact contribution verification
- Free-form
Otherchange type - Manual testing and qualified-human review
- Hosted CI checks without a successful hosted result
Do not annotate an unchecked human-only item as failed.
AI Artifact Sections
For changed .instructions.md, .prompt.md, .agent.md, or SKILL.md files, populate Sample
Prompts with a compact, natural request, a short execution summary, the user-visible output, and one
observable success signal. Keep preview content brief. Remove the section when it is not applicable
and the template permits deletion.
Select each AI artifact change type proven by changed paths. A SKILL.md change is a skill even
though it is Markdown. Leave Other for a human.
Testing And Checks
List only commands that ran, with their results. Do not list inferred or planned checks as passed. Leave the local validation aggregate unchecked when only targeted checks ran. Check documentation, naming, compatibility, and test-coverage items only when direct diff evidence proves the exact statement.
For security considerations:
- Leave the sensitive-information attestation for a human.
- Assess dependency security only when dependency manifests or lockfiles changed.
- Assess least privilege only when security-sensitive scripts or permission declarations changed.
Distribution Changes
When distributable Copilot artifact membership changed, add ## GHCP Membership Changes before
## Additional Notes. Determine membership from root plugin.json after required synchronization,
and list only added or removed artifacts. Mention npm run plugin:sync and
npm run plugin:validate in Validation when those commands ran.
Change Types
Infer types from branch and commit prefixes plus changed paths. Common mappings include:
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.
- 1mo ago Changed · -80 lines · -1,243 tokens per session 3a5aae04b038
- 1mo ago First seen · 147 lines · 1,835 tokens per session scan A 6cccda0134c1
hve-core pull-request.instructions.md is an instructions file published in the GitHub repository microsoft/hve-core (1,580 stars, last pushed yesterday), licensed MIT. It adds 592 tokens to every session, about $0.0024 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.