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/preflightgit 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/preflight)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/preflight"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/preflight.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.00018 | $0.00715 |
| Opus 5 | $0.00009 | $0.00358 |
| Sonnet 5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
preflight 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" -u "$JIRA_USER:$JIRA_API_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
node-team:preflight
Synopsis
/node-team:preflight [--fix]
Description
Tests all authentication tokens and CLI tools required by Node team workflows in a single pass. Reports pass/fail for each check so you can fix all auth issues at once instead of discovering them one at a time.
Run this before /node-team:setup, /node-cve:triage, or /node-bug:triage
to catch expired or missing credentials early.
Implementation
Run these checks in order and collect results:
1. GitHub CLI (gh)
gh auth status
- Pass: output contains "Logged in to github.com"
- Fail: not installed, not logged in, or token expired
2. GitHub API access
gh api user -q .login
- Pass: returns a username
- Fail: token lacks required scopes or is expired
3. Jira API token
Resolve the token using the same chain as jira.md (env var, macOS Keychain, Linux secret-tool):
JIRA_API_TOKEN="${JIRA_API_TOKEN:-$(security find-generic-password -s "JIRA_API_TOKEN" -w 2>/dev/null || secret-tool lookup service redhat key JIRA_API_TOKEN 2>/dev/null)}"
- Pass: non-empty value resolved
- Fail: no token found in any source
4. Jira API connectivity
curl -s -o /dev/null -w "%{http_code}" -u "$JIRA_USER:$JIRA_API_TOKEN" \
"https://redhat.atlassian.net/rest/api/3/myself"
- Pass: HTTP 200
- Fail: 401 (bad token), 403 (permissions), or connection error
5. Jira CLI (jira)
jira me
- Pass: returns current user info
- Fail: not installed or not configured (required by
node-cve;node-teamandnode-bugusecurldirectly)
Summary
Print a table of results:
Check Status
----- ------
GitHub CLI PASS
GitHub API PASS
Jira API token PASS
Jira API connectivity PASS
Jira CLI PASS (node-cve only)
If any required check fails and --fix is specified, print the remediation
steps for each failure (e.g., gh auth login, how to set JIRA_API_TOKEN).
If --fix is not specified, print a hint to re-run with --fix for guidance.
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 · 116 lines · 18 tokens per session scan A a846a77004e0
preflight is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 715 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-05.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
next
Suggest the most likely next workflow action based on current context.
weekly-summary
Generate weekly work summary from git activity.