backlog-execute

backlog-execute is a skill for Claude Code from microsoft/hve-core. It costs 36 tokens per session (2,781 once invoked), scanned A, original, MIT.

A command for creating or applying reviewed work-item changes in Azure DevOps, GitHub, or Jira, such as creating, updating, linking, transitioning, closing, or commenting on items.

In plain words
What is it for?
Use it to create one work item or execute a reviewed handoff file against a supported project tracker. Use a planning workflow for discovery or read-only backlog analysis.
Why use it?
It carries out approved backlog changes consistently while checking the target tracker and avoiding duplicate work when resuming an interrupted run.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions subagents.

Good fit Use it to create one work item or execute a reviewed handoff file against a supported project tracker. Use a planning workflow for discovery or read-only backlog analysis.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/hve-core/backlog-execute
About the project

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.

microsoft/hve-core · 1,606 stars · on GitHub

Install

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.

Any agent
npx skills add microsoft/hve-core --skill backlog-execute
Clone the repo
git clone --depth 1 https://github.com/microsoft/hve-core

Made for: Claude Code.

Wrote 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.

agentmods badge for backlog-execute

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-execute/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/backlog-execute)
Your own site
<a href="https://agentmods.dev/skills/microsoft/hve-core/backlog-execute"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-execute/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.

agentmods 80×15 button for backlog-execute

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/hve-core/backlog-execute"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/backlog-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,781 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 5 findings, 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 Prompt Injection · line 43
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 53
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 55
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Prompt Injection · line 57
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
  • medium Excessive Agency · line 78
    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.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.02781
Opus 5.5 $0.00014 $0.01112
Sonnet 5.5 $0.00007 $0.00556
Haiku 4.5 $0.00004 $0.00278

Measured 2mo ago against content hash b0a7685540fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backlog-execute 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.

.github/skills/project-planning/backlog-execute/SKILL.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backlog Execute

Mutating backlog execution for Azure DevOps, GitHub, and Jira. This command resolves the backing tracker at runtime and applies changes through the shared conventions and reference structure of the backlog-management skill.

Every operation this command runs is externally visible. The five safety protocols below are not optional refinements; they are the reason a single command can be trusted with write access to three trackers.

When to Use

  • Create a single work item through guided field collection.
  • Process a reviewed handoff file into sequential create, update, link, transition, close, and comment operations.
  • Resume an interrupted execution without duplicating completed work.

Use backlog-plan instead for discovery, triage, sprint planning, or any read-only analysis. A handoff file is normally produced there and reviewed by a human before it reaches this command.

Direct Invocation

This command is user-invocable. When a user runs it directly, build the missing context collaboratively rather than demanding a fully formed request. The bar for entry is low; the bar for mutating is not.

Infer what can be inferred safely, from the live conversation, an item key or URL the user names, the tracking root already present under .copilot-tracking/, the repository remote, and which platform credentials and tools are actually available. Confirm an inference before acting on it. Ask only for what is missing and mutation-critical, one focused question at a time rather than as an intake form.

Four things must hold before the first mutating call. Everything else can be discovered, inferred, or deferred:

  1. One platform, resolved and, if inferred, confirmed by the user.
  2. One destination, named and confirmed: an ADO project, a GitHub repository, or a Jira project key.
  3. A compatible write surface actually reachable in the active context.
  4. Any confirmation the autonomy tier requires for the operations at hand.

Supported direct-invocation contexts

Read the full file on GitHub · 176 lines

Changes

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.

  1. 2mo ago First seen · 176 lines · 36 tokens per session scan A b0a7685540fb

Subscribe to this mod's changes

backlog-execute is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 2,781 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.

Related

backlog-execute compared with skills from other repositories

backlog-execute next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
backlog-executemicrosoft/hve-coreSkill1.6ktodayMITA36Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code