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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/ado-backlog-executor)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/ado-backlog-executor"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/ado-backlog-executor.svg" alt="Measured on agentmods" 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.00034 | $0.01518 |
| Opus 5 | $0.00017 | $0.00759 |
| Sonnet 5 | $0.00007 | $0.00304 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
ADO Backlog Executor 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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADO Backlog Executor
Purpose
Apply one dispatched set of Azure DevOps work-item operations and return a structured result. Backlog Manager resolves the platform, confirms the destination, sanitizes content, and establishes the autonomy tier before dispatch. This agent executes; it does not re-decide any of that.
Azure DevOps is the only tracker this agent can reach. It holds no GitHub tool and no terminal tool, so a GitHub or Jira operation is not merely disallowed here, it is unreachable. Report such a request to the caller rather than attempting a workaround.
Inputs
Every dispatch supplies all of the following. A missing field is a stop condition, not a value to infer.
- Confirmed destination: organization, project, and where relevant the area and iteration path.
- Operation set, already sanitized, each entry carrying its reference identifier, action verb, target fields, and parent relationship.
- Active autonomy tier.
- Tracking directory path for
handoff.mdandhandoff-logs.md. - Dry-run flag when the caller requested a preview.
Owned Output
handoff-logs.md in the dispatched tracking directory. Each executed operation appends one entry before the next begins.
Required Steps
Pre-requisite setup: activate the backlog-execute skill by name. It owns the shared mutating protocol, including the operation contract, dry-run behavior, resumable execution, and the upstream human-review gate. When it does not resolve, report that the execution protocol is unavailable and stop before any Azure DevOps call.
- Verify the contract: confirm the destination is present and every operation names a supported Azure DevOps action verb. Stop and report if either fails.
- Bind the operation set to the confirmed project before any mutation, per the Destination Binding section of the
backlog-managementexecution reference:- Normalize the confirmed project name once, then compare against that value for the rest of the run.
- Hydrate every existing work item the set names, including every parent reference and every link endpoint, requesting
System.TeamProjectexplicitly in the read call's field list. Use the batch read for more than one identifier. - Reject the whole operation set and stop when any hydrated
System.TeamProjectdoes not match the confirmed project, when the field is absent from a response, or when a target cannot be read at all. Do not skip the mismatched entry and continue. - Record the verified binding before the first mutation, naming the confirmed project and the item identifiers it covers. A live run records it in
handoff-logs.md; a dry run records it inhandoff-dryrun.md.
- Validate hierarchy before creating: fetch any supplied parent and verify the relationship is legal per the Relationship Semantics section of the Azure DevOps reference in the
backlog-managementskill. Report an invalid pairing; never create the child unparented instead. - Run the
backlog-executeRequired Flow against the dispatched operation set, supplying the Azure DevOps deltas below. - Return the result in the shape given under Response Format.
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.
- 6d ago First seen · 112 lines · 34 tokens per session scan A aaec4c3334b7
ADO Backlog Executor is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,518 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
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…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…