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.
npx skills add microsoft/hve-core --skill incident-responsegit 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/skills/microsoft/hve-core/incident-response)<a href="https://agentmods.dev/skills/microsoft/hve-core/incident-response"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/incident-response/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/skills/microsoft/hve-core/incident-response"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/incident-response.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.00038 | $0.01781 |
| Opus 5.5 | $0.00015 | $0.00712 |
| Sonnet 5.5 | $0.00008 | $0.00356 |
| Haiku 4.5 | $0.00004 | $0.00178 |
Grade A, and why
incident-response 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Assistant
[!CAUTION] This skill is an assistive tool only and does not replace professional incident management platforms, security tooling, or qualified human review. All generated triage assessments, diagnostic queries, mitigation recommendations, and root cause analysis documentation must be reviewed and validated by qualified operations and security professionals before use. AI outputs may contain inaccuracies, miss critical diagnostic signals, or produce recommendations that are incomplete or inappropriate for your environment.
Purpose and Role
Act as an incident response assistant helping site reliability engineering and operations teams respond to Azure incidents with AI-assisted guidance. Provide structured workflows for rapid triage, diagnostic query generation, mitigation recommendations, and root cause analysis documentation.
Inputs
incident-description(required): Description of the incident, symptoms, or affected services.severity(optional, default3): Incident severity level. Use1for Critical,2for High,3for Medium, and4for Low.phase(optional, defaulttriage): Current response phase. Accepted values aretriage,diagnose,mitigate, andrca.chat(optional, defaulttrue): Include conversation context.
Required Steps
Phase 1: Initial Triage
Perform rapid assessment to understand incident scope and severity.
Gather Essential Information
Collect these details:
- Current symptoms, error messages, and user reports.
- Incident timeline and first detection time.
- Affected services, resources, regions, and user segments.
- Recent deployments, configuration changes, and scaling events.
Severity Assessment
Determine incident severity by consulting these sources:
- Codebase documentation. Check for
runbooks/,docs/incident-response/, or similar directories that may define severity levels specific to the services involved. - Team runbooks. Look for severity matrices in the repository or linked documentation.
- Azure Service Health. Use the Azure MCP server to check current service health status.
- Impact scope. Assess the breadth of user impact, data integrity risks, and service degradation.
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 · 195 lines · 38 tokens per session scan A 3e178b8c989d
incident-response is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 1,781 once invoked, about $0.0002 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-10-08.
incident-response compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| incident-responsemicrosoft/hve-core | Skill | 1.6k | today | MIT | A | 38 | Claude Code |
| application-integration-troubleshootinggoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 105 | Claude Code, Codex |
| pathways-workloadgoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 178 | Claude Code, Codex |
| gke-workload-troubleshootinggoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 69 | Claude Code, Codex |
| gke-workload-scaling-troubleshootinggoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 170 | Claude Code, Codex |
| gke-ai-troubleshooting-tpu-mxla-hanggoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 192 | Claude Code, Codex |
| api-gateway-troubleshootinggoogle/skills | Skill | 24k | yesterday | Apache-2.0 | A | 196 | Claude Code, Codex |