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 priority-rebalancegit 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/priority-rebalance)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/priority-rebalance"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/priority-rebalance/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/priority-rebalance"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/priority-rebalance.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.00025 | $0.00448 |
| Opus 5.5 | $0.00010 | $0.00179 |
| Sonnet 5.5 | $0.00005 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
priority-rebalance 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
When to Use
When the PO suspects priorities are stale, after a planning shift, or on a regular cadence.
Instructions
Read local/jira-workflow.md to understand priority values and conventions.
1. Query prioritized backlog
Pull all non-closed issues, grouped by current priority:
project = <PROJECT> AND status != Closed ORDER BY priority ASC, updated DESC
2. Analyze each priority tier
For each priority level (Blocker, Critical, Major, Normal, Minor), check:
- Inflation: Are there too many Blockers/Criticals? More than ~10% of the backlog at Blocker/Critical suggests priority inflation.
- Age vs priority: High-priority items that have been open for a long time without progress may need escalation or re-assessment.
- Blocking chains: Issues that block multiple other issues may deserve a priority bump regardless of their current level.
- Stale highs: Blocker/Critical issues with no recent updates — are they still urgent?
- Buried lows: Minor/Normal issues that are actually blocking high-priority work.
3. Present recommendations
## Priority Rebalance Suggestions — <date>
### Priority Inflation
- X of Y open issues are Blocker/Critical (Z%)
- Recommendation: Review these for downgrade...
### Suggested Upgrades
- ISSUE-123 (currently Normal) → Major
- Reason: Blocks 3 other in-progress issues
### Suggested Downgrades
- ISSUE-456 (currently Blocker) → Major
- Reason: No updates in 30 days, no downstream blockers
### Stale High-Priority
- ISSUE-789 (Blocker) — last updated 21 days ago
- Still a blocker? Needs PO decision.
### Summary
- Current distribution: X Blocker, Y Critical, Z Major, ...
- Suggested distribution: ...
All changes require PO approval. Offer to apply approved changes via Jira API.
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 First seen · 59 lines · 25 tokens per session scan A 6fec78d57dec
priority-rebalance is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 448 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 skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…