Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/openshift-eng/two-node-toolboxnpx agentmods add commands/openshift-eng/two-node-toolbox/quick_referenceWrote 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/two-node-toolbox/quick_reference)<a href="https://agentmods.dev/commands/openshift-eng/two-node-toolbox/quick_reference"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/quick_reference/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/openshift-eng/two-node-toolbox/quick_reference"><img src="https://agentmods.dev/badge/commands/openshift-eng/two-node-toolbox/quick_reference.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.03657 |
| Opus 5.5 | $0.00000 | $0.01463 |
| Sonnet 5.5 | $0.00000 | $0.00731 |
| Haiku 4.5 | $0.00000 | $0.00366 |
Grade D, and why
QUICK_REFERENCE scanned grade D with 3 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 1mo 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.
ansible cluster_vms -i deploy/openshift-clusters/inventory.ini -m shell -a "sudo pcs status" -b Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"sudo rm -rf /var/lib/etcd/*" -b Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"curl -k -u <user>:<pass> https://<bmc-ip>/redfish/v1/Systems" -b How it starts
The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Etcd TNF Quick Reference Guide
Fast troubleshooting for common etcd issues on Two-Node with Fencing clusters
Use this guide for quick diagnosis and remediation. For detailed analysis, refer to TROUBLESHOOTING_SKILL.md.
CRITICAL: Target the Correct Hosts
Always use cluster_vms host group for etcd/Pacemaker commands:
- ✓ Correct:
ansible cluster_vms -i inventory.ini -m shell -a "pcs status" -b - ✗ Wrong:
ansible all -i inventory.ini ...(would include hypervisor) - ✗ Wrong:
ansible hypervisor -i inventory.ini ...(hypervisor has no etcd)
The hypervisor is only for VM lifecycle (virsh/kcli). All etcd operations run on cluster_vms.
Quick Diagnostics
Collect all diagnostics automatically:
./helpers/etcd/collect-all-diagnostics.sh
Check cluster health quickly:
# Pacemaker status (on cluster VMs)
ansible cluster_vms -i deploy/openshift-clusters/inventory.ini -m shell -a "sudo pcs status" -b
# Etcd member list (on cluster VMs)
ansible cluster_vms -i deploy/openshift-clusters/inventory.ini -m shell -a "sudo podman exec etcd etcdctl member list -w table" -b
# OpenShift etcd operator (if cluster access available)
oc get co etcd -o yaml | grep -A10 "status:"
Check workload distribution during failover:
# Quick check: functional pods per node (uses simple grep)
oc get pods -owide -n <namespace> | grep Running | grep <node_name> | wc -l
# Detailed analysis: shows READY status to filter stale pod references
oc get pods -n <namespace> \
-o custom-columns='NAME:.metadata.name,STATUS:.status.phase,READY:.status.conditions[?(@.type=="Ready")].status,NODE:.spec.nodeName'
# Count only functional workloads
oc get pods -n <namespace> \
-o custom-columns='NAME:.metadata.name,STATUS:.status.phase,READY:.status.conditions[?(@.type=="Ready")].status,NODE:.spec.nodeName' \
| grep 'True.<node_name>' | wc -l
💡 Key Insight: During failover scenarios, pod status can show stale references. Use READY=True filter or the simple grep approach to see actual functional workloads. STATUS=Running + READY=False indicates stale pod references from failed nodes.
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.
- 1mo ago First seen · 403 lines · 0 tokens per session scan D 4bdf863350a5
QUICK_REFERENCE is a command published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,657 tokens. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.