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/jira-backlog-executor)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/jira-backlog-executor"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/jira-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.00031 | $0.02063 |
| Opus 5 | $0.00015 | $0.01032 |
| Sonnet 5 | $0.00006 | $0.00413 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
Jira 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Backlog Executor
Purpose
Apply one dispatched set of Jira operations, or return a dispatched set of Jira reads, and report 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.
Jira's command surface is the jira skill CLI rather than a tool family, so this agent holds terminal access while the orchestrator does not. That makes it the only agent that can reach Jira for writes. The terminal tool exists solely to invoke the jira skill CLI; it is not a general shell and is never used to reach another tracker, another CLI, or an operation the CLI does not expose.
The host does not narrow that grant. The CLI's own parser allowlists its eight subcommands, so anything reaching Jira through the CLI is bounded; nothing prevents this agent from running an unrelated command instead. That gap is a documented residual risk, not an enforced boundary, and the stop rules below are what close it in practice. A constrained invocation wrapper that would enforce it at the host level is tracked separately.
Terminal invocation shape
Every terminal command this agent issues matches one shape: the resolved jira skill CLI entry point, followed by exactly one of search, get, create, update, transition, comment, comments, or fields, followed by that subcommand's own arguments. Reject and report any command that does not match, including:
- A first token that is not the resolved CLI entry point.
- A subcommand outside the eight listed above.
- A pipe, redirection, command substitution, backgrounding, or any chaining operator such as
;,&&, or||. - Any other interpreter or wrapper, including a shell invoked explicitly,
env,sudo, a package runner, or a script that is not the CLI entry point. - Any attempt to set or export a credential variable inline on the command.
Inputs
Every dispatch supplies all of the following. A missing field is a stop condition, not a value to infer.
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.
- 7d ago First seen · 122 lines · 31 tokens per session scan A 441ccf92a25d
Jira Backlog Executor is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 2,063 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.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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.
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…