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 skills add bmbouter/redhat-agents --skill backlog-health-checkgit 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/skills/bmbouter/redhat-agents/backlog-health-check)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/backlog-health-check"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/backlog-health-check/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/skills/bmbouter/redhat-agents/backlog-health-check"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/backlog-health-check.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.00030 | $0.00441 |
| Opus 5 | $0.00015 | $0.00220 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
backlog-health-check 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 9d 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
When to Use
When the PO wants to clean up the backlog, before grooming, or on a regular cadence.
Instructions
Read local/jira-workflow.md to understand required fields, statuses, and conventions.
1. Query open issues
Pull all non-closed issues in the project. Use JQL:
project = <PROJECT> AND status != Closed ORDER BY updated ASC
2. Check for problems
For each issue, check:
- Stale: Not updated in 14+ days while in an active status (In Progress, Refinement). Flag with days-since-update.
- Missing required fields: Check against the required fields from the workflow config (priority, component, description, acceptance criteria, etc.).
- Orphaned: Non-epic issues without a parent epic, if the workflow config says sub-issues under epics are the norm.
- Wrong status: Issues that appear stuck — e.g., "In Progress" with no assignee, or "New" for 30+ days.
- Potential duplicates: Issues with very similar summaries. Group candidates.
3. Report
Present findings grouped by problem type:
## Backlog Health Report — <date>
### Stale Issues (no update in 14+ days)
- ISSUE-123 — "Summary" — 23 days stale, status: In Progress, assignee: @person
### Missing Fields
- ISSUE-456 — missing: component, acceptance criteria
- ISSUE-789 — missing: priority
### Orphaned Issues (no parent epic)
- ISSUE-012 — "Summary"
### Possible Duplicates
- Group 1: ISSUE-111, ISSUE-222 — both about "widget rendering"
### Summary
- X issues checked
- Y problems found
- Z issues are healthy
Ask the PO which items they want to address and help fix them.
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.
- 9d ago First seen · 59 lines · 30 tokens per session scan A d85b6474dd30
backlog-health-check is a skill published in the GitHub repository bmbouter/redhat-agents (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30 tokens to every session and 441 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.