generate-tuned-profile

generate-tuned-profile is a command for Claude Code from openshift-eng/ai-helpers. It costs 21 tokens per session (2,337 once invoked), scanned A, original, Apache-2.0.

A command that creates a Tuned profile manifest for the OpenShift Node Tuning Operator. The manifest is a YAML file describing node settings such as system parameters and which nodes should receive them.

In plain words
What is it for?
Use it to create version-controlled profiles with sysctl, bootloader, service, and node-selection settings.
Why use it?
It reduces the need to hand-edit complex multi-line YAML when creating or changing node performance profiles.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 plugins/node-tuning/skills/scripts/generate_tuned_profile.py \.

Part of the node-tuning plugin — 1 skill, 2 commands shipped together

Good fit Use it to create version-controlled profiles with sysctl, bootloader, service, and node-selection settings.

Compare 6 commands from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/openshift-eng/ai-helpers
agentmods
npx agentmods add commands/openshift-eng/ai-helpers/generate-tuned-profile

Made for: Claude Code.

Or install node-tuning, the plugin that ships this one along with the rest of its 1 skill, 2 commands.

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.

agentmods badge for generate-tuned-profile

README.md
[![agentmods](https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate-tuned-profile/github.svg)](https://agentmods.dev/commands/openshift-eng/ai-helpers/generate-tuned-profile)
Your own site
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/generate-tuned-profile"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate-tuned-profile/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.

agentmods 80×15 button for generate-tuned-profile

Your own site · 80×15
<a href="https://agentmods.dev/commands/openshift-eng/ai-helpers/generate-tuned-profile"><img src="https://agentmods.dev/badge/commands/openshift-eng/ai-helpers/generate-tuned-profile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,337 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.02337
Opus 5 $0.00010 $0.01169
Sonnet 5 $0.00004 $0.00467
Haiku 4.5 $0.00002 $0.00234

Measured 7d ago against content hash c06ff999d6aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

generate-tuned-profile 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 7d 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.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/node-tuning/commands/generate-tuned-profile.md · 201 lines

How it starts

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

Name

node-tuning:generate-tuned-profile

Synopsis

/node-tuning:generate-tuned-profile [profile-name] [--summary TEXT] [--include VALUE ...] [--sysctl KEY=VALUE ...] [--match-label KEY[=VALUE] ...] [options]

Description

The node-tuning:generate-tuned-profile command streamlines creation of tuned.openshift.io/v1 manifests for the OpenShift Node Tuning Operator. It captures the desired Tuned profile metadata, tuned daemon configuration blocks (e.g. [sysctl], [variables], [bootloader]), and recommendation rules, then invokes the helper script at plugins/node-tuning/skills/scripts/generate_tuned_profile.py to render a ready-to-apply YAML file.

Use this command whenever you need to:

  • Bootstrap a new Tuned custom profile targeting selected nodes or machine config pools
  • Generate manifests that can be version-controlled alongside other automation
  • Iterate on sysctl, bootloader, or service parameters without hand-editing multi-line YAML

The generated manifest follows the structure expected by the cluster Node Tuning Operator:

apiVersion: tuned.openshift.io/v1
kind: Tuned
metadata:
  name: <profile-name>
  namespace: openshift-cluster-node-tuning-operator
spec:
  profile:
  - data: |
      [main]
      summary=...
      include=...
      ...
    name: <profile-name>
  recommend:
  - machineConfigLabels: {...}
    match:
    - label: ...
      value: ...
    priority: <priority>
    profile: <profile-name>

Implementation

  1. Collect inputs
    • Confirm Python 3.8+ is available (python3 --version).
    • Gather the Tuned profile name, summary, optional include chain, sysctl values, variables, and any additional section lines (e.g. [bootloader], [service]).
    • Determine targeting rules: either --match-label entries (node labels) or --machine-config-label entries (MachineConfigPool selectors).
    • Decide whether an accompanying MachineConfigPool (MCP) workflow is required for kernel boot arguments (see Advanced Workflow below).
    • Use the helper's --list-nodes and --label-node flags when you need to inspect or label nodes prior to manifest generation.

Read the full file on GitHub · 201 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.

  1. 7d ago First seen · 201 lines · 21 tokens per session scan A c06ff999d6aa

Subscribe to this mod's changes

generate-tuned-profile is a command published in the GitHub repository openshift-eng/ai-helpers (116 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 2,337 once invoked, about $0.0001 per session on Opus 5. 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-09-05.