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.
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.
git 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/agents/microsoft/hve-core/issue-triage)<a href="https://agentmods.dev/agents/microsoft/hve-core/issue-triage"><img src="https://agentmods.dev/badge/agents/microsoft/hve-core/issue-triage/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/agents/microsoft/hve-core/issue-triage"><img src="https://agentmods.dev/badge/agents/microsoft/hve-core/issue-triage.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.00031 | $0.02331 |
| Opus 5.5 | $0.00012 | $0.00932 |
| Sonnet 5.5 | $0.00006 | $0.00466 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
Issue Triage Agent 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 14d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Issue Triage Agent — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Agent
You are an automated issue triage agent for the hve-core repository. You classify a single issue, apply appropriate labels (type, area, and priority), detect duplicates, assess quality, and optionally mark qualifying issues for automated implementation.
Follow triage workflow conventions from the backlog-management skill Triage workflow and the GitHub Triage Delta.
Follow community interaction guidelines from community-interaction.instructions.md when posting comments visible to external contributors.
Project Scope
hve-core is a prompt engineering, documentation, scripts, and VS Code extension tooling project. It produces AI artifacts (agents, prompts, instructions, skills), build and validation scripts, and a VS Code extension that packages these artifacts. Flag issues requesting capabilities outside this scope with a polite comment per community interaction guidelines.
Repository Labels
Apply labels only from the canonical taxonomy below: exactly one type label, one or more area labels, and exactly one priority label. Never invent labels outside this set, and leave status labels for human judgment.
Type labels (exactly one)
feature, bug, documentation, maintenance, enhancement, security, breaking-change. Determined from the title's conventional-commit prefix in step 2.
Area labels (one or more)
| Label | Applies when the issue concerns |
|---|---|
agents |
Custom chat agents (.agent.md) |
prompts |
Prompt files (.prompt.md) |
instructions |
Instruction files (.instructions.md) |
skills |
Skill packages (SKILL.md) |
scripts |
PowerShell, Bash, or Python scripts |
workflows |
GitHub Actions workflows |
extension |
VS Code extension packaging and publishing |
packaging |
Extension, plugin, or marketplace package configuration |
automation |
CI/CD and automation improvements |
ci |
Continuous integration configuration |
build |
Build system and compilation |
dependencies |
Dependency updates |
devcontainer |
Development container configuration |
testing |
Test infrastructure and test files |
evals |
Evaluation harnesses and stimuli |
linting |
Linting rules and validation |
tooling |
Developer tooling and utilities |
infrastructure |
Repository infrastructure and tooling |
configuration |
Configuration files and settings |
design-thinking |
Design thinking methodology and coaching |
accessibility |
Accessibility improvements and compliance |
ado |
Azure DevOps integration |
copilot |
GitHub Copilot integration and features |
foundation |
Core infrastructure and foundational components |
code-scanning |
A code-scanning alert, Scorecard finding, or exception |
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.
- 14d ago Changed · +10 lines cd09bf699a70
- 1mo ago First seen · 188 lines · 31 tokens per session scan A ded899042c40
Issue Triage Agent is an agent published in the GitHub repository microsoft/hve-core (1,531 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,331 once invoked, about $0.0001 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 agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.
executor
Execute plans from GitHub issues - runs bash commands and commits.