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/categorize-activity-type)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/categorize-activity-type"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/categorize-activity-type/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/categorize-activity-type"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/categorize-activity-type.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.00010 | $0.00615 |
| Opus 5.5 | $0.00004 | $0.00246 |
| Sonnet 5.5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
categorize-activity-type 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
jira:categorize-activity-type
Synopsis
/jira:categorize-activity-type <issue-key> [--auto-apply]
Description
Analyzes a single JIRA ticket and assigns an Activity Type category based on ticket content, issue type, labels, and parent context. Classification logic is shared with /jira:batch-categorize-activity-types via the categorize-activity-types skill.
Implementation
Phase 1: Fetch Ticket Data
Use MCP to fetch the issue by key. Delegate to the categorize-activity-types skill in single-issue mode.
See skills/categorize-activity-types/SKILL.md for the full classification methodology, including fields to fetch, classification rules, validation, and reporting.
Phase 2: Apply Update (Conditional)
Auto-apply logic:
-
If
--auto-applyflag present AND confidence is High:- Automatically update Activity Type field
- Display confirmation to user
-
Otherwise (no flag OR confidence is Medium/Low):
- Present suggestion to user
- Ask for confirmation before applying
- If user confirms, proceed with update
- If user declines, exit without changes
Arguments
-
$1 - issue-key (required)
- JIRA issue key to categorize
- Format: PROJECT-NUMBER (e.g., ROX-12345, OCPBUGS-67890)
-
--auto-apply (optional)
- Automatically apply Activity Type when confidence is High
- Without this flag, always prompts user for confirmation
- Medium/Low confidence always requires manual confirmation
Examples
-
Basic categorization (manual confirmation):
/jira:categorize-activity-type ROX-12345 -
Auto-apply for high confidence:
/jira:categorize-activity-type ROX-12345 --auto-apply -
Process security vulnerability:
/jira:categorize-activity-type ROX-28072 --auto-applyExpected: Issue Type = Vulnerability -> "Security & Compliance" (High confidence, auto-applied)
Return Value
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 · 80 lines · 10 tokens per session scan A e989ed521d76
categorize-activity-type is a command published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 615 once invoked, about $0.0000 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.