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 backlog-plangit 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/backlog-plan)<a href="https://agentmods.dev/skills/microsoft/hve-core/backlog-plan"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-plan/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/backlog-plan"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 57 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00037 | $0.01727 |
| Opus 5.5 | $0.00015 | $0.00691 |
| Sonnet 5.5 | $0.00007 | $0.00345 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
backlog-plan 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 2mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Plan
Read-only backlog planning for Azure DevOps, GitHub, and Jira. This command resolves the backing tracker at runtime, selects a planning mode, and executes it through the shared conventions and reference structure of the backlog-management skill. It produces planning files that a separate execution pass acts on.
This command never mutates a tracker. It creates, updates, and reads files under the platform tracking root, and it reads from the tracker. Every create, update, transition, link, close, and comment belongs to backlog-execute.
When to Use
Use this command to plan backlog work on any supported platform:
- Discover candidate work from a user request, a set of documents, or a search.
- Retrieve the work assigned to you and enrich it into an implementation-ready handoff.
- Triage existing items and recommend field, label, priority, or status changes.
- Plan a sprint, iteration, or milestone against coverage, capacity, dependencies, and gaps.
- Resume an interrupted planning workflow from its durable artifacts.
Use backlog-execute instead when the intent is to apply changes to a tracker. Use functional-planner instead when the input is a PRD and the output is a work-item hierarchy.
Required Flow
Step 1: Resolve the platform
Run the Platform Resolution section of the backlog-management skill before any planning work. Carry its resolved platform and readiness verdict forward. When resolution is ambiguous, resolve it there rather than assuming a tracker here.
Every mode below is read-only, so a platform inferred from preflight success may proceed without the confirmation a mutating workflow requires.
Step 2: Select the planning mode
Classify the request into exactly one mode. When the argument names a mode, use it. Otherwise infer from these signals, and when two modes remain plausible, state both with a brief rationale and ask.
| Mode | Signals | Protocol |
|---|---|---|
discover |
discover, find, search, extract, gaps, roadmap, backlog brief, from a document | Discovery workflow in the workflows reference |
my-work |
my items, assigned to me, my queue, what am I working on | Stage 1 of the task-planning reference |
task-plan |
task planning, prepare for implementation, hand off to research | Stage 2 of the task-planning reference |
triage |
triage, classify, categorize, prioritize, duplicates, untriaged | Triage workflow in the workflows reference plus the platform's Triage Delta |
sprint |
sprint, iteration, milestone, release, capacity, velocity, coverage | The sprint-planning reference plus the platform's Sprint Planning Delta |
resume |
resume, continue, next step, suggest, where was I | Resumption below |
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.
- 2mo ago First seen · 111 lines · 37 tokens per session scan A 2a0db007564c
backlog-plan is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,727 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.
backlog-plan compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| backlog-planmicrosoft/hve-core | Skill | 1.6k | today | MIT | A | 37 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |