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/overviewgit 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/overview)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/overview"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/overview.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.1 | $0.00013 | $0.00783 |
| Opus 5 | $0.00006 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
overview 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 yesterday.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
node-team:overview
Synopsis
/node-team:overview [--sub-team core|devices|kueue]
Description
Displays a comprehensive overview of the OpenShift Node team: what the team owns, its responsibilities, component and repo mappings, sub-team structure, ceremonies, upstream community involvement, active sprints, and which specialized plugins handle which domain.
This is the entry point for understanding the Node team's scope and navigating to the right tool for a given task.
Implementation
-
Read shared references:
- Team mission, responsibilities, ceremonies, Slack channels, customer support tools, key links, and plugin routing from shared/team-info.md
- Component list and repo mappings from shared/components.md
- Sub-team assignments from the sub-teams table in
shared/components.md - Sprint and board info from jira.md
- OCP-to-K8s version mapping from shared/version-map.md
-
If
--sub-teamis specified, filter the Component Ownership table and Sub-teams table to that sub-team's components. All other sections (ceremonies, Slack channels, upstream communities, key links, plugin routing) are always shown in full since they apply team-wide. -
Present a structured summary with these sections from the references:
- Team Mission and Responsibilities (from
team-info.md) - Component Ownership table (from
components.md) - Sub-teams table (from
components.md). If roster files exist at~/.node-assistant/team-roster-{core,dra,kueue}.json, include member count per sub-team. - Ceremonies and sprint cadence (from
team-info.md) - Upstream Communities (from
team-info.md) - Slack Channels and Mailing Lists (from
team-info.md) - Customer Support Tools (from
team-info.md) - Active Sprints (best-effort): query the Jira Agile API (board 11478) for active sprints per jira.md. List sprint names and dates. If the API call fails (missing credentials, network issues), print "Sprint data unavailable" and continue with the remaining sections.
- Version Mapping: show the current OCP-to-K8s version mapping from
shared/version-map.mdfor the latest 2-3 OCP releases. - Plugin Routing table (from
team-info.md) - Key Links (from
team-info.md)
- Team Mission and Responsibilities (from
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.
- yesterday First seen · 89 lines · 13 tokens per session scan A 0d63a9e7a844
overview is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 783 once invoked, about $0.0001 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-09-05.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.