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/checklist)<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/checklist"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/checklist.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.00016 | $0.02577 |
| Opus 5 | $0.00008 | $0.01288 |
| Sonnet 5 | $0.00003 | $0.00515 |
| Haiku 4.5 | $0.00002 | $0.00258 |
Grade B, and why
checklist scanned grade B with 2 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 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- If the check fails or no check exists, show instructions and ask the user Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| VPN connectivity | `curl -s -o /dev/null -w "%{http_code}" --connect-timeout 5 https://brewweb.engineering.redhat.com/brew/` (expect 200) | Connect to Red Hat VPN | How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
node-onboarding:checklist
Synopsis
/node-onboarding:checklist [--track dev|qe] [--resume] [--check-only]
Description
Walks a new Node team member through the full onboarding process: access requests, tool installation, environment setup, and first cluster creation. The command runs automated checks to verify each step that can be tested programmatically. For manual steps, it provides instructions and links, then asks the user to confirm completion.
Progress is saved between sessions so the checklist can be resumed later.
Implementation
Phase 0: Setup and Argument Parsing
- Parse arguments:
--track dev|qe: onboarding track (default:dev). Theqetrack adds QE-specific items after the common sections.--resume: load prior progress from~/.node-assistant/onboarding-progress.jsonand skip completed sections.--check-only: run only automated verification checks without interactive prompts. Print pass/fail for each checkable item.
- If
--resume, read~/.node-assistant/onboarding-progress.json. If the file does not exist, start fresh. - Read the checklist structure from references/onboarding-checklist.md.
Phase 1: Interactive Checklist
Walk through each section sequentially. For each item:
- If an automated check is defined, run it and report the result.
- If the check passes, mark the item complete automatically.
- If the check fails or no check exists, show instructions and ask the user
to confirm when done (skip this prompt in
--check-onlymode). - Save progress to
~/.node-assistant/onboarding-progress.jsonafter each section completes.
Sections:
1. Prerequisites
Verify the user has completed New Hire Orientation and has basic access.
| Item | Automated Check | Manual Action |
|---|---|---|
| Spin-up Buddy assigned | None | Request your manager to assign a Spin-up Buddy before starting |
| VPN connectivity | curl -s -o /dev/null -w "%{http_code}" --connect-timeout 5 https://brewweb.engineering.redhat.com/brew/ (expect 200) |
Connect to Red Hat VPN |
| Jira access | curl -s -o /dev/null -w "%{http_code}" -u "${JIRA_USER:-$(git config user.email)}:$JIRA_API_TOKEN" "https://redhat.atlassian.net/rest/api/3/myself" (expect 200) |
Set up JIRA_API_TOKEN per jira.md |
| ServiceNow portal | curl -s -o /dev/null -w "%{http_code}" --connect-timeout 5 https://redhat.service-now.com/help (expect 200) |
Verify access to https://redhat.service-now.com/help?id=rh_requests |
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 · 242 lines · 16 tokens per session scan B 84b725d02756
checklist is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,577 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks the agent to reveal its instructions, 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
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
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.