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/permissionsgit 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.01877 |
| Opus 5 | $0.00000 | $0.00938 |
| Sonnet 5 | $0.00000 | $0.00375 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
PERMISSIONS scanned grade A with 0 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 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Etcd Troubleshooting Skill - Permission Configuration
This document defines the permission grants for the etcd troubleshooting skill to enable faster diagnostics without requiring user approval for read-only operations.
Active Configuration
The project includes a .claude/settings.json file with pre-configured permissions for etcd troubleshooting. These permissions are automatically applied when using Claude Code in this repository.
Note: These permissions apply project-wide (not skill-specific) because Claude Code's permission system operates at the project level. However, since this repository is dedicated to two-node toolbox operations, granting read-only diagnostic permissions is appropriate for all use cases.
To customize permissions for your environment, create or edit .claude/settings.local.json (gitignored) to override project defaults.
Permission Philosophy
Automatic (No User Approval Required):
- Read-only operations on diagnostic data
- File reading from diagnostic output directories
- Basic Ansible fact gathering (no changes)
- OpenShift cluster status queries (read-only)
Requires User Approval:
- Any operation that modifies cluster state
- Running Ansible playbooks (except validation)
- Executing remediation scripts
- Pacemaker resource operations (cleanup, restart, etc.)
Granted Permissions
Bash Tool - Read-Only Commands
The following Bash commands are automatically approved for execution without user permission:
# File reading operations
Bash(cat:*) # Read any file
Bash(head:*) # Read beginning of files
Bash(tail:*) # Read end of files
Bash(less:*) # Page through files
# File searching and filtering
Bash(grep:*) # Search file contents
Bash(find:*) # Find files
Bash(ls:*) # List directory contents
# Diagnostic data inspection
Bash(jq:*) # Parse JSON output
Bash(yq:*) # Parse YAML output
# Git read-only operations
Bash(git log:*) # View git history
Bash(git status:*) # Check git status
Bash(git diff:*) # View differences
# Ansible read-only operations
Bash(ansible cluster_vms -i * -m ping) # Test connectivity
Bash(ansible cluster_vms -i * -m setup) # Gather facts
Bash(ansible *_master_* -i * -m shell -a "cat *") # Read files via Ansible
Bash(ansible *_master_* -i * -m shell -a "grep *") # Search files via Ansible
Bash(ansible *_master_* -i * -m shell -a "tail *") # Read file ends via Ansible
Bash(ansible *_master_* -i * -m shell -a "pcs status*") # Read Pacemaker status
Bash(ansible *_master_* -i * -m shell -a "pcs resource status*") # Read resource status
Bash(ansible *_master_* -i * -m shell -a "podman ps*") # List containers
Bash(ansible *_master_* -i * -m shell -a "podman exec etcd etcdctl member list*") # Read member list
Bash(ansible *_master_* -i * -m shell -a "podman exec etcd etcdctl endpoint health*") # Check health
Bash(ansible *_master_* -i * -m shell -a "podman exec etcd etcdctl endpoint status*") # Check status
Bash(ansible *_master_* -i * -m shell -a "crm_attribute --query*") # Query CIB attributes
Bash(ansible *_master_* -i * -m shell -a "journalctl*") # Read system logs
Bash(ansible *_master_* -i * -m shell -a "systemctl status*") # Check service status
# OpenShift read-only operations (via oc-wrapper or with proxy sourcing)
Bash(source deploy/openshift-clusters/proxy.env && oc get*) # Read cluster resources
Bash(source deploy/openshift-clusters/proxy.env && oc describe*) # Describe resources
Bash(source deploy/openshift-clusters/proxy.env && oc logs*) # Read pod logs
Bash(*oc-wrapper.sh get*) # Get resources via wrapper
Bash(*oc-wrapper.sh describe*) # Describe resources via wrapper
Bash(*oc-wrapper.sh logs*) # Read logs via wrapper
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 · 198 lines · 0 tokens per session scan A 7ed601212900
PERMISSIONS 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 1,877 tokens. A static security scan graded it A with 0 findings. 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.