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/readmegit 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.00000 | $0.03067 |
| Opus 5 | $0.00000 | $0.01533 |
| Sonnet 5 | $0.00000 | $0.00613 |
| Haiku 4.5 | $0.00000 | $0.00307 |
Grade B, and why
README scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo pcs resource cleanup etcd # All nodes How it starts
The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Etcd Troubleshooting Skill for Two-Node Clusters
This directory contains the etcd/Pacemaker troubleshooting skill for Claude Code, designed specifically for two-node OpenShift clusters with fencing topology.
Overview
The etcd troubleshooting skill enables Claude to interactively diagnose and resolve etcd and Pacemaker issues on two-node clusters. It provides:
- Automated diagnostic data collection from cluster VMs and OpenShift
- Systematic analysis frameworks for identifying root causes
- Step-by-step remediation procedures
- Verification and prevention recommendations
Directory Structure
.claude/commands/etcd/
├── README.md # This file
├── PROJECT.md # Project specification and checklist
├── QUICK_REFERENCE.md # Fast troubleshooting guide (START HERE)
├── TROUBLESHOOTING_SKILL.md # Detailed skill definition and guidelines
├── ../../../helpers/etcd/ # Helper scripts and playbooks
│ ├── validate-cluster-access.sh # Validate both Ansible and oc access
│ ├── collect-all-diagnostics.sh # Master orchestration script
│ ├── oc-wrapper.sh # oc wrapper with proxy.env handling
│ └── playbooks/ # Ansible playbooks
│ ├── validate-access.yml # Validate Ansible connectivity
│ └── collect-diagnostics.yml # Collect VM-level diagnostics
├── etcd-ops-guide/ # Etcd operations documentation
│ ├── clustering.md
│ ├── recovery.md
│ ├── monitoring.md
│ ├── failures.md
│ └── ... (other etcd docs)
└── pacemaker/ # Pacemaker documentation
├── podman-etcd.txt # Resource agent (fetched from upstream)
└── Pacemaker_Administration/ # Pacemaker admin guides
Quick Start
For Fast Troubleshooting
Start with QUICK_REFERENCE.md for common issues and immediate fixes.
The quick reference covers:
- Common failure patterns with instant fixes
- One-command diagnostics
- Step-by-step remediation for 7 most frequent issues
- Quick verification checklist
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 · 419 lines · 0 tokens per session scan B 30dc72bf738e
README is a command published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 28d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,067 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.