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/pull-requestgit 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.01835 | $0.01835 |
| Opus 5 | $0.00918 | $0.00918 |
| Sonnet 5 | $0.00367 | $0.00367 |
| Haiku 4.5 | $0.00184 | $0.00184 |
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 yesterday.
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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Conventions
Repository-specific conventions for pull request generation in hve-core. Follow #file:hve-core/pull-request.instructions.md for the pull request generation workflow.
Template Integration
When a repository template exists, keep unfilled placeholders for manual completion.
Rich markdown formatting is permitted within all sections, including ### sub-headings, bold, italics, blockquotes, and prose paragraphs.
Report that the repository template was used once generation completes.
Manual-Only Sections
These sections require human verification. The agent does not modify them:
- AI artifact contribution verification checkboxes (under the checklist section)
- HVE Builder review attestation checkbox (under type of change)
- Free-form other type checkbox (under type of change)
Section Fill Guidance
Sample Prompts
When AI artifact changes are detected (.instructions.md, .prompt.md, .agent.md, SKILL.md), fill sub-sections from pr-reference-log.md analysis:
| Sub-section | Content Source |
|---|---|
| User Request | Describe how to trigger or invoke the modified artifact |
| Execution Flow | Summarize key steps, tool usage, and decision points |
| Output Artifacts | List files or content created with brief previews |
| Success Indicators | Describe how users verify correct operation |
[!NOTE] Human review is recommended for agent-populated Sample Prompts content.
Leave the section empty with placeholder comments intact when the PR does not include AI artifact changes.
Testing
Document all testing performed by the agent:
- List each automated validation command run in Step 7 and its pass/fail status.
- Summarize security analysis findings.
- Summarize diff-based assessments performed.
- Note that manual testing was not performed when applicable.
[!NOTE] Add manual testing descriptions when applicable.
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.
- yesterday 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,405 stars, last pushed 2d ago), licensed MIT. It adds 1,835 tokens to every session, about $0.0092 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.