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 commands/openshift-eng/ai-helpers/backloggit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/commands/openshift-eng/ai-helpers/backlog)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/backlog"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/backlog.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 | $0.00016 | $0.05146 |
| Opus 5 | $0.00008 | $0.02573 |
| Sonnet 5 | $0.00003 | $0.01029 |
| Haiku 4.5 | $0.00002 | $0.00515 |
Grade A, and why
backlog scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
This command uses direct REST API calls (via `curl`) instead of MCP tools because MCP has performance issues when fetching large datasets — tool result size limits cause 413 errors, and processing hundreds of tickets thr Copies of this mod
1 near-identical copy found in the catalogue:
- backlog — 89% identical, 169 lines differ
How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:backlog
Synopsis
/jira:backlog [project-key] [--assignee username] [--days-inactive N]
Description
The jira:backlog command helps identify suitable tickets from the JIRA backlog to work on by intelligently analyzing unassigned tickets and bot-assigned tickets. Unlike simple filtering, this command reads ticket descriptions, comments, and activity patterns to recommend the best candidates for work.
Key Feature: The command selects 2 tickets from each priority level (Critical, High, Normal, Low) that are actually available to pick up (unassigned or assigned to bots only), giving you a balanced view across all priorities so you can choose based on your expertise and preference.
Important: This command only recommends tickets that are unassigned or assigned to bots (like "OCP DocsBot"). Tickets assigned to real people are excluded, even if they have no recent activity, because they may already be claimed by someone.
This command is particularly useful for:
- Finding tickets to work on when you have available capacity
- Identifying unassigned or abandoned tickets that need attention
- Getting a mix of priorities to choose from (not just critical)
- Understanding ticket context before starting work
How it works:
- Searches for unassigned tickets or tickets with no activity for 28+ days (configurable)
- Filters for availability - keeps only unassigned or bot-assigned tickets
- Analyzes ticket content - reads descriptions, comments, and activity patterns
- Evaluates suitability - identifies tickets that are ready vs. need verification vs. may be abandoned
- Selects intelligently - chooses the most suitable 2 tickets from each priority level
- Provides comprehensive summaries with recommendations for each ticket
Prerequisites
This command uses direct REST API calls (via curl) instead of MCP tools because MCP has performance issues when fetching large datasets — tool result size limits cause 413 errors, and processing hundreds of tickets through MCP commands creates excessive context usage.
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.
- 2d ago First seen · 492 lines · 16 tokens per session scan A dbb55de8a23b
backlog is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 5,146 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.