What is migrate-k8-config?

A migration command that converts several legacy DevOps configuration files into a unified YAML configuration and a separate secrets file for k8-lib tools.

Use it to read existing project configuration, generate k8-util-config.yaml and .k8-secrets.yaml, and note missing source files during migration.

It reduces the manual work and inconsistency involved in combining environment, deployment tier, namespace, timeout, and secret settings into the newer format.

migrate-k8-config — Command for Claude Code by noizu-labs-ml

Install

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.

Clone the repo

git clone --depth 1 https://github.com/noizu-labs-ml/NoizuPromptLingo

Made for: Claude Code.

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/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config/github.svg)](https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config)

Your own site

<a href="https://agentmods.dev/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config/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/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config"><img src="https://agentmods.dev/badge/commands/noizu-labs-ml/noizupromptlingo/migrate-k8-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,214 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01214
Opus 5.5	$0.00000	$0.00486
Sonnet 5.5	$0.00000	$0.00243
Haiku 4.5	$0.00000	$0.00121

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

Security

Grade A, and why

migrate-k8-config 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 2mo 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.

commands/migrate-k8-config.md · 103 lines

How it starts

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

Migrate Legacy Config to k8-util-config.yaml

Convert a project's legacy DevOps configuration files into the unified k8-util-config.yaml + .k8-secrets.yaml format used by k8-lib tools.

Instructions

You are migrating legacy config files to the new unified YAML format. Follow these steps exactly.

Step 1: Locate Legacy Files

Find and read these files at the project root (the directory containing .git):

File	Required	Format
`config.env`	yes	Shell `KEY=VALUE` exports
`tiers.yaml`	yes	YAML with `.tiers[].charts[]`
`namespaces.conf`	yes	`release-name=namespace` per line
`timeout-overrides.conf`	yes	`chart-name=timeout` per line
`.envrc`	optional	Shell exports (may contain secrets to extract)

If any are missing, note it and proceed with what exists.

Step 2: Read the Schema Template

Read the example file for reference:

utilities/devops/k8-lib/k8-util-config.yaml.example
utilities/devops/k8-lib/.k8-secrets.yaml.example

Step 3: Generate k8-util-config.yaml

Create k8-util-config.yaml at the project root with these rules:

apiVersion: k8-lib/v1 at the top
secrets_file: .k8-secrets.yaml pointer
paths section — compute relative paths from the config file to:
- helm_dir: where Helm charts live (usually helm)
- terraform_dir: Terraform root (usually terraform)
- projects_dir: where project.yaml files are discovered
aws section — from config.env K8_AWS_PROFILE, K8_AWS_REGION. Do NOT include K8_AWS_ACCOUNT_ID (goes in secrets).
docker section — from K8_DOCKER_REGISTRY
kubernetes section — from K8_NAMESPACE, K8_STAGING_NAMESPACE, K8_INFRA_NAMESPACE
infisical section — host and project_id only. client_id/client_secret go in secrets file.
terraform section — from K8_TF_STATE_BUCKET, K8_TF_KMS_ALIAS, K8_TF_LOCK_TABLE, K8_TF_IMPORT_USER, K8_TF_IMPORT_POLICY_NAME
helm section — oci_registry and registry_host only. registry_user goes in secrets.
preferences section — from K8_DIFF_VIEWER, K8_ADMIN_EMAIL, K8_CREDENTIALS_LINK
database section — from K8_DB_NAME, K8_DB_USER_PREFIX, K8_PGBOUNCER_HOST (if present)
status_patterns section — from K8_STATUS_*_PATTERN variables (if present)
tiers section — copy the .tiers array from tiers.yaml verbatim
namespace_overrides section — convert namespaces.conf KEY=VALUE lines to YAML map:
```
infisical=infisical  →  infisical: infisical
shared-postgres=data-ns  →  shared-postgres: data-ns
```
Skip comment lines (starting with #) and blank lines.
timeout_overrides section — convert timeout-overrides.conf the same way:
```
vllm=120m  →  vllm: 120m
```

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

2mo ago First seen · 103 lines · 0 tokens per session scan A 5330b29c00ac

Subscribe to this mod's changes

migrate-k8-config is a command published in the GitHub repository noizu-labs-ml/NoizuPromptLingo (13 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,214 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-09-04.

Cloud DevOps and cloud

migrate-k8-config next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
migrate-k8-confignoizu-labs-ml/NoizuPromptLingo	Command	13	10d ago	MIT	A	0	Claude Code
cost-optimizewshobson/agents	Command	42k	yesterday	MIT	A	26	Claude Code
deploybutterbase-ai/butterbase-skills	Command	535	6d ago	MIT	A	20	Claude Code
envvercel/vercel-plugin	Command	326	yesterday	none	A	35	Claude Code
firebase-publishPierry/harness-kit	Command	4	1mo ago	MIT	A	20	Claude Code
scanprajapatimehul/claude-aws-cost-saver	Command	24	4mo ago	MIT	A	6	Claude Code
migrationdatabayt/hogwarts	Command	18	3d ago	none	A	4	Claude Code