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/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/batch-categorize-activity-types)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/batch-categorize-activity-types"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/batch-categorize-activity-types/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/commands/openshift-eng/ai-helpers/batch-categorize-activity-types"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/batch-categorize-activity-types.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.00016 | $0.00739 |
| Opus 5.5 | $0.00006 | $0.00296 |
| Sonnet 5.5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
batch-categorize-activity-types 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:batch-categorize-activity-types
Synopsis
/jira:batch-categorize-activity-types <project-key> [--type Epic] [--limit 100] [--jql 'AND status != Closed'] [--dry-run]
Description
Fetches all Jira issues in a project that have no Activity Type set, categorizes each into one of six Sankey capacity allocation categories, validates results, generates a report, and (with user approval) applies the updates back to Jira.
Classification logic is shared with /jira:categorize-activity-type via the categorize-activity-types skill.
Implementation
Delegate to the categorize-activity-types skill in batch mode. The skill handles all phases: gather, classify, validate, report, apply, and iterate.
See skills/categorize-activity-types/SKILL.md for the full workflow.
If --dry-run is set, instruct the skill to skip Phase 4 (apply).
Arguments
-
$1 - project-key (required)
- Jira project key (e.g., OCM, ARO, ROX)
-
--type <issue-type> (optional, default: Epic)
- Issue type to filter. Supports: Epic, Story, Task, Bug, etc.
-
--limit <number> (optional, default: 100)
- Maximum number of issues to fetch and classify per batch
-
--jql <conditions> (optional)
- Additional JQL conditions appended to the base query
- Example:
'AND resolved >= "2025-01-01"' - Example:
'AND status != Closed'
-
--dry-run (optional)
- Run classification and generate report without applying updates to Jira
Examples
-
Classify all Epics in OCM:
/jira:batch-categorize-activity-types OCM -
Classify Stories instead of Epics:
/jira:batch-categorize-activity-types ARO --type Story -
Add JQL filter:
/jira:batch-categorize-activity-types OCM --jql 'AND resolved >= "2025-01-01"' -
Dry run (classify and report, don't apply):
/jira:batch-categorize-activity-types ROX --dry-run
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 · 85 lines · 16 tokens per session scan A 34fb6a21006f
batch-categorize-activity-types is a command published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 739 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.