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/kuadrant/mcp-gateway/sync-chartgit clone --depth 1 https://github.com/Kuadrant/mcp-gatewayWrote 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/kuadrant/mcp-gateway/sync-chart)<a href="https://agentmods.dev/commands/kuadrant/mcp-gateway/sync-chart"><img src="https://agentmods.dev/badge/commands/kuadrant/mcp-gateway/sync-chart.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 | $0.00000 | $0.00640 |
| Opus 5 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
sync-chart 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Helm Chart Templates
Verify and update Helm chart templates to match the source manifests in config/mcp-system.
Steps
1. Sync CRDs (automated)
Run the existing make targets:
make generate-all
make check
2. Compare source manifests to chart templates
Read and compare these file pairs:
| Source (config/mcp-system/) | Chart Template (charts/mcp-gateway/templates/) |
|---|---|
| deployment-broker.yaml | deployment-broker.yaml |
| deployment-controller.yaml | deployment-controller.yaml |
| rbac.yaml | rbac.yaml |
| broker-service.yaml | service.yaml |
Files intentionally NOT synced (kustomize-only or optional):
- namespace.yaml (Helm uses .Release.Namespace)
- kustomization.yaml (kustomize metadata)
- *-patch.yaml files (kustomize overlays)
- redis-*.yaml (optional component, not in base chart)
- httproute.yaml (cluster-specific)
- trusted-header-public-key.yaml (cluster-specific)
3. For each file pair
- Read the source manifest from config/mcp-system/
- Read the existing chart template from charts/mcp-gateway/templates/
- Compare the structural elements (containers, ports, volumes, RBAC rules, etc.)
- Identify differences that need updating in the chart template
4. Update chart templates preserving Helm patterns
When updating templates, preserve these Helm conventions:
Metadata:
metadata:
name: {{ include "mcp-gateway.fullname" . }}-suffix
namespace: {{ .Release.Namespace }}
labels:
{{- include "mcp-gateway.labels" . | nindent 4 }}
Images:
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
Controller images:
image: "{{ .Values.imageController.repository }}:{{ .Values.imageController.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.imageController.pullPolicy }}
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.
- 3d ago First seen · 96 lines · 0 tokens per session scan A 1f377a0daa34
sync-chart is a command published in the GitHub repository Kuadrant/mcp-gateway (97 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 640 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-30.
Other commands, from other repositories
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
overview
Unified cost dashboard combining state, plan, actual costs, projected costs, drift, and recommendations.
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.