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/ci-owned-validation.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/ci-owned-validation)<a href="https://agentmods.dev/instructions/microsoft/hve-core/ci-owned-validation"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/ci-owned-validation/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/ci-owned-validation"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/ci-owned-validation.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.00739 | $0.00739 |
| Opus 5.5 | $0.00296 | $0.00296 |
| Sonnet 5.5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
hve-core ci-owned-validation.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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI-Owned Validation Instructions
Keep ordinary local validation predictable while preserving direct, named reproduction of CI-owned lanes.
Command taxonomy
- Use
lint:*for non-mutating static checks. - Use
format:*or an explicit fixer suffix for mutating cleanup. - Use
validate:*for non-mutating aggregates composed only of locally safe checks. - Use
test:*for locally safe deterministic or component tests. - Use
ci:*for CI-owned or otherwise non-default validation lanes, including eval-framework execution and documentation Playwright E2E.
The ci:* prefix communicates ownership and default agent behavior. It does not block direct local execution and requires no marker, wrapper, or opt-in flag.
Selection and composition
- Generic validation uses applicable local-safe commands such as
validate:local,validate:docs, or targeted checks. It does not selectci:*commands. - Changed-area preflight may inspect a matching workflow's
ci:*wrapper to identify and run its locally safe non-mutating child checks when no equivalent local-safe package command exists. This reproduces component checks, not the CI lane; do not infer browsers, services, credentials, moderation, or other lane-specific prerequisites. - A task that specifically asks to run or reproduce a named CI lane may invoke its ordinary
ci:*command after its prerequisites and side effects are understood. - Keep
validate:*aggregates free ofci:*commands, fixers, generators, installers, browser actions, and interactive children. - Keep report generation noninteractive. Use a separately named
:openor:uicommand for browser or interactive behavior. - Do not restore removed
eval:*,lint:all,lint:docs-site,docs:test:e2e*, or nestedtest:e2e*compatibility aliases.
Package and workflow changes
- Coordinate a breaking package-script rename with every owning workflow consumer in the same change set.
- Preserve workflow change detection, gates, arguments, outputs, artifacts, summaries, permissions, and failure behavior when changing only an entry-point name.
- Keep agent-conformance suite orchestration and its
workflow_callinvocation unchanged unless a separate requirement justifies a package entry point. - Use existing repository syntax, workflow, and source checks plus hosted CI evidence. Do not add a command-policy test subsystem or dedicated policy job solely for this taxonomy.
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 · +1 lines · +65 tokens per session 99257aaa55ee
- 1mo ago First seen · 43 lines · 674 tokens per session scan A bb01947b863c
hve-core ci-owned-validation.instructions.md is an instructions file published in the GitHub repository microsoft/hve-core (1,580 stars, last pushed yesterday), licensed MIT. It adds 739 tokens to every session, about $0.0030 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.