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.
git clone --depth 1 https://github.com/kubestellar/kubestellar-mcpWrote 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/kubestellar/kubestellar-mcp/kustomize)<a href="https://agentmods.dev/commands/kubestellar/kubestellar-mcp/kustomize"><img src="https://agentmods.dev/badge/commands/kubestellar/kubestellar-mcp/kustomize.svg" alt="Measured on agentmods" 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.00348 |
| Opus 5 | $0.00000 | $0.00174 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
kustomize 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.
What it actually says
Kustomize
Apply kustomize configurations to multiple clusters.
Usage
Build and apply kustomize overlays to one or more clusters.
Examples
- "Apply kustomize from ./overlays/production to all clusters"
- "Build kustomize output from ./base"
- "Delete resources defined in ./overlays/staging kustomize"
What it does
- Builds kustomize output from the specified path
- Applies (or deletes) the rendered manifests to target clusters
- Reports success/failure per cluster
MCP Tools Used
kustomize_build- Render kustomize output without applyingkustomize_apply- Build and apply to clusterskustomize_delete- Build and delete those resources
Implementation
Use the kustomize_apply tool with:
path: Path to directory containing kustomization.yaml (required)dry_run: Preview without applyingclusters: Target clusters (all if not specified)
Examples of Tool Calls
Build only:
{
"path": "./overlays/production"
}
Apply to all clusters:
{
"path": "./overlays/production",
"dry_run": false
}
Delete from specific clusters:
{
"path": "./overlays/staging",
"clusters": ["staging-1", "staging-2"]
}
Prerequisites
Requires either:
kustomizeCLI installed- Or
kubectlwith kustomize support (kubectl kustomize)
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.
- 7d ago First seen · 64 lines · 0 tokens per session scan A 98fcd7d621ea
kustomize is a command published in the GitHub repository kubestellar/kubestellar-mcp (2 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 348 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
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.