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 agents/microsoft/hve-core/issue-triagegit 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.00031 | $0.02113 |
| Opus 5 | $0.00015 | $0.01056 |
| Sonnet 5 | $0.00006 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00211 |
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 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.
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 — 188 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 |
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 · 188 lines · 31 tokens per session scan A ded899042c40
Issue Triage Agent is an agent published in the GitHub repository microsoft/hve-core (1,411 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,113 once invoked, about $0.0002 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 agents, from other repositories
product-owner
Protect scope, enforce story ordering, and ensure value delivery stays on track. Prevent scope creep, gold-plating, and out-of-order implementation.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.