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/peter-n91/hve-squad-mcp/github-backlog-executorgit clone --depth 1 https://github.com/Peter-N91/hve-squad-mcpWhat 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.00035 | $0.01313 |
| Opus 5 | $0.00017 | $0.00656 |
| Sonnet 5 | $0.00007 | $0.00263 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
GitHub 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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Backlog Executor
Purpose
Apply one dispatched set of GitHub issue 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.
GitHub is the only tracker this agent can reach. It holds no Azure DevOps tool and no terminal tool, so an Azure DevOps or Jira operation is unreachable rather than merely disallowed. 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: owner and repository.
- Operation set, already sanitized, each entry carrying its reference identifier, action verb, target fields, labels, and any parent issue.
- 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 GitHub call.
- Verify the contract: confirm the destination is present and every operation names a supported GitHub action verb. Stop and report if either fails.
- Validate before creating: discover valid issue types and labels for the repository rather than assuming a fixed set. Fetch any supplied parent issue and verify the sub-issue relationship is legal per the GitHub reference in the
backlog-managementskill. - Run the
backlog-executeRequired Flow against the dispatched operation set, supplying the GitHub 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.
- yesterday First seen · 107 lines · 35 tokens per session scan A 7ed18d1f44e0
GitHub Backlog Executor is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,313 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
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…