What is two-node-toolbox AGENTS.md?

Project instructions for Two-Node Toolbox, a deployment framework for setting up OpenShift clusters with two nodes in development and test environments.

Use them when deploying or managing OpenShift clusters, including arbiter, fencing, and single-node setups on AWS.

They give an coding agent the project context, common commands, and deployment procedures needed to work safely in the repository.

How openshift-eng/two-node-toolbox configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to openshift-eng/two-node-toolbox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/openshift-eng/two-node-toolbox/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/openshift-eng/two-node-toolbox

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/openshift-eng/two-node-toolbox/agents-md/github.svg)](https://agentmods.dev/instructions/openshift-eng/two-node-toolbox/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/openshift-eng/two-node-toolbox/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift-eng/two-node-toolbox/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/openshift-eng/two-node-toolbox/agents-md"><img src="https://agentmods.dev/badge/instructions/openshift-eng/two-node-toolbox/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,901 This file is loaded in full into every session.

When invoked 2,901 The same file — it is already loaded in full.

Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02901	$0.02901
Opus 5.5	$0.01160	$0.01160
Sonnet 5.5	$0.00580	$0.00580
Haiku 4.5	$0.00290	$0.00290

Measured 2d ago against content hash d46b6dd2d403, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

two-node-toolbox AGENTS.md scanned grade C 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 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.

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 key automatically read from `~/.ssh/id_ed25519.pub` on ansible controller

AGENTS.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project Overview

Two-Node Toolbox (TNF) is a comprehensive deployment automation framework for OpenShift two-node clusters in development and testing environments. The project supports multiple deployment methods and virtualization platforms, with a focus on "Two-Node with Arbiter" and "Two-Node with Fencing" topologies.

Common Commands

Deployment Operations

# From the deploy/ directory:

# Deploy AWS hypervisor and cluster in one command
make deploy arbiter-ipi   # Deploy arbiter topology cluster
make deploy fencing-ipi   # Deploy fencing topology cluster
make deploy sno-ipi       # Deploy Single Node OpenShift (IPI method)
make deploy sno-agent     # Deploy Single Node OpenShift (Agent method)
make deploy fencing-assisted   # Deploy hub + spoke TNF via assisted installer

# Instance lifecycle management
make create              # Create new EC2 instance
make init               # Initialize deployed instance
make start              # Start stopped EC2 instance
make stop               # Stop running EC2 instance
make destroy            # Destroy EC2 instance and resources

# Cluster operations
make redeploy-cluster   # Redeploy OpenShift cluster using dev-scripts
make shutdown-cluster   # Shutdown cluster VMs
make startup-cluster    # Start cluster VMs and proxy
make clean             # Clean OpenShift cluster
make full-clean        # Complete cleanup including cache
make patch-nodes        # Build resource-agents RPM and patch cluster nodes

# Utilities
make ssh               # SSH into EC2 instance
make status            # Show status dashboard (instance, cluster VMs, proxy, cluster API); 'make info' is an alias
make inventory         # Update inventory.ini with current instance IP
make doctor            # Validate configuration and prerequisites (read-only)
make doctor <type>     # Validate strictly for a specific cluster type (e.g. fencing-kcli)

# Installation preparation (resolve image + generate config)
# /prepare tnf ipi aws 4.21     # Claude skill — interactive or agent-driven
helpers/resolve-release-image.sh --version 4.21        # Resolve version → pullspec
helpers/prepare-config.sh --topology fencing --method ipi --release-image <pullspec> --ci-token <token>

Read the full file on GitHub · 301 lines

Changes

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 Changed · +1 tokens per session d46b6dd2d403
1mo ago Changed · +5 lines · +78 tokens per session ca1aa90fa46e
2mo ago First seen · 296 lines · 2,822 tokens per session scan C 3c222ea25eee

Subscribe to this mod's changes

two-node-toolbox AGENTS.md is an instructions file published in the GitHub repository openshift-eng/two-node-toolbox (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 2,901 tokens to every session, about $0.0116 per session on Opus 5.5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

two-node-toolbox AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
two-node-toolbox AGENTS.mdopenshift-eng/two-node-toolbox	Instructions file	5	3d ago	Apache-2.0	C	2,901	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

two-node-toolbox: Instructions file for Codex