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/docusaurus-edits.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/docusaurus-edits)<a href="https://agentmods.dev/instructions/microsoft/hve-core/docusaurus-edits"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/docusaurus-edits/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/docusaurus-edits"><img src="https://agentmods.dev/badge/instructions/microsoft/hve-core/docusaurus-edits.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.01695 | $0.01695 |
| Opus 5.5 | $0.00678 | $0.00678 |
| Sonnet 5.5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
hve-core docusaurus-edits.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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docusaurus Content Instructions
These instructions apply automatically when editing any file under docs/. Follow them to maintain consistency across the documentation site.
Frontmatter
Every documentation page requires these frontmatter fields. npm run lint:frontmatter fails when any of them is missing or empty, and the check runs in PR validation:
title: Page title displayed in the browser tab and sidebardescription: One-sentence summary for SEO and social sharingauthor: Author or team responsible for the contentms.date: Last review or update date inYYYY-MM-DDformatms.topic: One ofoverview,concept,tutorial,reference,how-to,troubleshooting,architecturekeywords: Non-empty list of content categorization terms
Optional fields:
sidebar_position: Integer controlling page order within its category (1, 2, 3...)sidebar_label: Override the sidebar display text when it should differ fromtitletags: Array of tags for content categorizationestimated_reading_time: Positive integer in minutes
---
title: The RPI Workflow
description: How the Research-Plan-Implement-Review loop structures AI-assisted development
author: Microsoft
ms.date: 2026-08-04
ms.topic: concept
keywords:
- rpi
- research
- plan
- implement
- review
sidebar_position: 2
sidebar_label: RPI Workflow
tags: [build-the-work, rpi, workflow]
---
Update ms.date to the current date whenever you review or change a page.
Two subtrees follow different rules:
- Architecture Decision Records under
docs/planning/adrs/are governed byadr-frontmatter.schema.json. They usetagsfor categorization and must not declarekeywords. - Pages under
docs/reference/are generated bynpm run docs:generate, which emits the required fields automatically. Do not hand-edit their frontmatter.
Admonitions
Both Docusaurus admonitions (:::note, :::tip, :::warning) and GitHub-style alerts (> [!NOTE], > [!TIP], > [!WARNING]) are supported. GitHub-style alerts render correctly in Docusaurus via remark-github-blockquote-alert and on GitHub natively. Prefer GitHub-style alerts for content that must render on both platforms.
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 First seen · 223 lines · 1,695 tokens per session scan A 5d005b162297
hve-core docusaurus-edits.instructions.md is an instructions file published in the GitHub repository microsoft/hve-core (1,580 stars, last pushed yesterday), licensed MIT. It adds 1,695 tokens to every session, about $0.0068 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.