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/two-node-toolbox/setupgit clone --depth 1 https://github.com/openshift-eng/two-node-toolboxWhat 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 | $0.00009 | $0.03724 |
| Opus 5 | $0.00005 | $0.01862 |
| Sonnet 5 | $0.00002 | $0.00745 |
| Haiku 4.5 | $0.00001 | $0.00372 |
Grade D, and why
setup scanned grade D 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 for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- User needs to provide: host IP, SSH user, optional sudo password Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- `~/.ssh/id_ed25519.pub` (preferred) How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping a user set up the two-node-toolbox repository for the first time. Guide them through the configuration process step by step.
Command Arguments
The user may specify what they want to configure:
/setupor/setupwith no args: Ask what to configure (default: aws + dev-scripts)/setup external: Configure external host only/setup aws: Configure AWS hypervisor only/setup kcli: Configure kcli installation only/setup dev-scripts: Configure dev-scripts installation only/setup all: Configure all four options Present the options in categories. external and aws are in the "hypervisor" category. kcli and dev-scripts are in the "installer" category.
Your Task
Based on the argument provided (or user's interactive choice), guide them through configuring the selected deployment method(s). For each selected method:
- Check current state - Verify what's already configured
- Explain prerequisites - Check if required tools/files are present
- Guide file setup - Help copy templates and configure files (ONE STEP AT A TIME)
- Provide resource links - Give URLs for external resources they need
- Validate configuration - Check if files are properly set up
- Suggest next steps - Provide commands to run next
Shared Prerequisites
SSH Key Check
All deployment methods require an SSH key on the local machine. Check for any of these files:
~/.ssh/id_ed25519.pub(preferred)~/.ssh/id_rsa.pub- Any
~/.ssh/id_*.pubfile
If no SSH key exists, create one with: ssh-keygen -t ed25519 -f ~/.ssh/id_ed25519
Note for non-default key paths: Set SSH_PUBLIC_KEY in config/instance.env. This is used by both the AWS hypervisor and dev-scripts deployments.
Inventory File
Required for: external, kcli, dev-scripts (not AWS - it auto-generates inventory)
- File: deploy/openshift-clusters/inventory.ini
- Template: deploy/openshift-clusters/inventory.ini.sample
- Check if it exists and has been edited (differs from sample)
- User needs to provide: host IP, SSH user, optional sudo password
- Suggest copying:
cp deploy/openshift-clusters/inventory.ini.sample deploy/openshift-clusters/inventory.ini
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 · 333 lines · 9 tokens per session scan D 4621964a2fab
setup is a command published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 28d ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,724 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.