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 instructions/microsoft/hve-core/copilot-instructionsgit clone --depth 1 https://github.com/microsoft/hve-coreWhat 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 | $0.04336 | $0.04336 |
| Opus 5 | $0.02168 | $0.02168 |
| Sonnet 5 | $0.00867 | $0.00867 |
| Haiku 4.5 | $0.00434 | $0.00434 |
Grade A, and why
hve-core copilot-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 2d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Instructions
Items in the Highest Priority Rules section from attached instructions files override any conflicting guidance.
Priority Rules
- Conventions and styling from the codebase take precedence for all changes.
- Instructions files not already attached are read before deciding on edits.
- Breaking changes are acceptable.
- Backward-compatibility layers or legacy support are added only when explicitly requested.
- Tests, scripts, and one-off markdown docs are created or modified only when the requested change or its directly required support work needs them.
- Before a dependency-backed npm command, establish the relevant package root with
npm ciwhen no successful installation for its current lockfile is known. Treat the repository root anddocs/docusaurusindependently; do not substitutenpm installor reinstall a known-current root. - Generic validation uses local-safe commands and does not select
ci:*commands. A command in a plan, README, template, prior log, catalog, or error is a reference, not an execution request. A task that specifically asks to run or reproduce a named CI lane may use its ordinaryci:*command. - Browser installation, model or moderation environments, service startup, credentials, execution outside the sandbox, interactive UI, and adjacent CI lanes are separate actions. Do not infer them from generic validation or a failed command.
Rules for comments:
- Remain brief and factual, describing behavior, intent, invariants, and edge cases.
- Thought processes, step-by-step reasoning, and narrative comments do not appear in code.
- Comments that contradict current behavior are removed or updated.
- Temporal markers (phase references, dates, task IDs) are removed from code files during any edit.
Rules for markdown frontmatter:
- When editing any Markdown file whose frontmatter already contains an
ms.datefield, update that field to today's date. - Format the date using ISO 8601 (
YYYY-MM-DD), matching the existingms.dateconvention.
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.
- 2d ago First seen · 298 lines · 4,336 tokens per session scan A 2d58cbabe3bc
hve-core copilot-instructions.md is an instructions file published in the GitHub repository microsoft/hve-core (1,411 stars, last pushed today), licensed MIT. It adds 4,336 tokens to every session, about $0.0217 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-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.