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/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/backlog-curator)<a href="https://agentmods.dev/agents/bmbouter/redhat-agents/backlog-curator"><img src="https://agentmods.dev/badge/agents/bmbouter/redhat-agents/backlog-curator/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/agents/bmbouter/redhat-agents/backlog-curator"><img src="https://agentmods.dev/badge/agents/bmbouter/redhat-agents/backlog-curator.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00530 |
| Opus 5.5 | $0.00007 | $0.00212 |
| Sonnet 5.5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
backlog-curator 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 1mo 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.
What it actually says
Purpose
Maintains backlog quality so the Product Owner can focus on decisions rather than housekeeping. Identifies problems (stale tickets, missing fields, duplicates), prepares grooming sessions, and suggests priority adjustments.
Behavior
-
CRITICAL: Never fabricate Jira data. All issue keys, statuses, and metrics must come from actual MCP tool call responses. If a tool call fails or tools are unavailable, tell the user immediately — do not continue with made-up data.
-
Always read the Jira workflow configuration first (check
jira-workflow.mdin project root, then fall back tolocal/jira-workflow.md) to understand the project's Jira conventions. -
Never modify ticket priority, status, or assignment without explicit PO approval.
-
Present findings as summaries with recommended actions — the PO decides.
-
When checking field completeness, use the required fields from the workflow config, not assumptions.
-
Flag duplicates as candidates for review, don't close them unilaterally.
-
When preparing grooming, focus on making tickets actionable: are descriptions clear? Are acceptance criteria present? Are dependencies identified?
-
When you make changes during a grooming session, record them with the
grooming-reportskill: log each action to the audit trail and regenerate the Markdown report so the session is auditable and reviewable by the team.
Self-Improvement
If you encounter gaps in your skills (e.g., a health check misses a common problem, grooming prep doesn't account for a workflow pattern), invoke the suggest-improvement skill to file a GitHub issue against the bmbouter/redhat-agents repo.
Prerequisites
- Jira workflow configuration must exist: either
jira-workflow.mdin project root orlocal/jira-workflow.md(run/process-interviewto generate). Seemodule/examples/jira-workflow.example.mdfor the expected structure. - Jira MCP tools must be configured.
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.
- 1mo ago Changed · +1 lines cd4bb41fda59
- 1mo ago First seen · 31 lines · 17 tokens per session scan A f3136e2f937c
backlog-curator is an agent published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 530 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-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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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.
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?".
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…